Feature blockers:
Versioning <https://blueprints.launchpad.net/fuel/+spec/nailgun-versioning>
for REST API
<https://blueprints.launchpad.net/fuel/+spec/nailgun-versioning-api>, UI,
serialization
<https://blueprints.launchpad.net/fuel/+spec/nailgun-versioning-rpc>

Ongoing activities:
Nailgun plugins
<https://blueprints.launchpad.net/fuel/+spec/nailgun-plugins>

Stability and Reliability:
Docs for serialization data
Docs for REST API data
<https://blueprints.launchpad.net/fuel/+spec/documentation-on-rest-api-input-output>
Nailgun unit tests restructure
Image based provisioning
<https://blueprints.launchpad.net/fuel/+spec/image-based-provisioning>
Granular deployment
<https://blueprints.launchpad.net/fuel/+spec/granular-deployment-based-on-tasks>
Artifact-based build system
Power management
Fencing <https://blueprints.launchpad.net/fuel/+spec/ha-fencing>

Features:
Advanced networking
<https://blueprints.launchpad.net/fuel/+spec/advanced-networking> (blocked
by Multi L2 support)

Some of this items will not fit 6.0, I guess. But we should work on them
now.



On Thu, Aug 28, 2014 at 4:26 PM, Mike Scherbakov <mscherba...@mirantis.com>
wrote:

> Hi Fuelers,
> while we are busy with last bugs which block us from releasing 5.1, we
> need to start thinking about upcoming releases. Some of you already started
> POC, some - specs, and I see discussions in ML and IRC.
>
> From overall strategy perspective, focus for 6.0 is:
>
>    - OpenStack Juno release
>    - Certificate 100-node deployment. In terms of OpenStack, if not
>    possible for Juno, let's do for Icehouse
>    - Send anonymous stats about deployment (deployment modes, features
>    used, etc.)
>    - Stability and Reliability
>
> Let's take a little break and think, in a first order, about features,
> sustaining items and bugs which block us from releasing whether 5.1.1 or
> 6.0.
> We have to start creating blueprints (and moving them to 6.0 milestone)
> and make sure there are critical bugs assigned to appropriate milestone, if
> there are any.
>
> Examples which come to my mind immediately:
>
>    - Use service token to auth in Keystone for upgrades (affects 5.1.1),
>    instead of plain admin login / pass. Otherwise it affects security, and
>    user should keep password in plain text
>    - Decrease upgrade tarball size
>
> Please come up with blueprints and LP bugs links, and short explanation
> why it's a blocker for upcoming releases.
>
> Thanks,
> --
> Mike Scherbakov
> #mihgen
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to