[Starlingx-discuss] StarlingX cutting over to containers

[Curtis]

On Thu, Feb 28, 2019 at 2:13 PM Miller, Frank <Frank.Miller at windriver.com>
wrote:

> StarlingX Community:
>
>
>
> I am pleased on behalf of the entire containers subteam to announce that
> the StarlingX project is ready to use containerized services.  The subteam
> has pulled together a ton of feature devlopment, integration, testing and
> issue resolution to achieve stability in our four major configurations.
> Sanities are passing on these configs in both a no proxy/no mirror
> environment as well as in a proxy/mirror environment.  Scott will be
> merging the f/stein feature branch onto master Friday morning and all
> builds after that point will only support a containers configuration
> [1,2].  *We would ask that community members hold off merging commits
> during the day on Friday.  *
>
>
>
> There will be some expected limitations at this point in the project as
> there are a number of planned stories still in progress and a number of
> medium or lower priority LPs open.  However, we are confident that we are
> ready to get a wider use across the community. For more information on
> containers including the recipe to bring up containers, current limitations
> and an FAQ see: https://wiki.openstack.org/wiki/StarlingX/Containers
>

Thanks all! This is awesome to see. :)

Thanks,
Curtis



>
>
> Frank
>
> Containers Project Lead
>
>
>
> [1] The config_controller script will now only support bringing up the
> platform services in containers
>
> [2] the –kubernetes option for config_controller is being removed as the
> script will only support a containers configuration as of Friday
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>


-- 
Blog: serverascode.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190301/200ca52d/attachment.html>