fuel-dev team mailing list archive

[Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>]

Hi, Prakash


We are following openstack deployment workflow, thus all features are
tracked in the blueprints. Ideally, you need to follow Fuel Contribution
Guide here
https://wiki.openstack.org/wiki/Fuel/Where_to_contribute#Suggest_enhancements,
create a blueprint in Fuel project Launchpad
space<https://blueprints.launchpad.net/fuel>and fill in the
specification document. We are using Fuel
Design Document
Template<https://docs.google.com/a/mirantis.com/document/d/1KlTTM0X-v9nVxyG1ZSdOEpf_yj4EtzNL1Q9Sd4v5DX0/edit>on
Google Drive. You can easily copy and use it.

Here we will need to negotiate all the parts of plugins inclusion process,
e.g.:

what are the use cases
which plugins are we going to integrate
which parts of deployment process are affected:
do we need any modification of base operating system provisioning
which misc libraries and services we are going to install and configure
which parts of OpenStack configuration we need to modify
how is High Availability is going to be implemented
which parts of Nailgun engine we need to modify in order to calculate
values of data structures we are going to pass to deployment engine, e.g.
which networking, volume managers and other parts are affected, which new
node roles (e.g. controller, compute, network node, etc.) we need to
implement
how deployment process is orchestrated, e.g. which roles are deployed in
which sequence
which part of the UI we need to modify, ideally including some UI mockups
how we are going to do acceptance testing of this feature

During this design document drafting we will discuss all the details of
implementation, split it into milestones and target them for particular
releases.

Feel free to ask any questions if your experience any difficulties in
openstack-dev maling list (openstack-dev@xxxxxxxxxxxxxxxxxxx), but do not
forget to add "[Fuel][Brocade]" prefix into email subject as we are
specifically filtering these emails as related to our project. Also, we are
available in #fuel-dev IRC channel on freenode. Also, be aware that
significant part of our engineers reside in Moscow and Kharkiv time zone
and plan your communications with us taking this into account.

Looking forward to questions from you.




On Tue, Apr 22, 2014 at 1:35 AM, Prakash Kaligotla <pkaligot@xxxxxxxxxxx>wrote:

> Two other questions
>
>
>
> 1.       We are of the understanding that we will be receiving certain
> test scripts that need to be executed as part of certification process. How
> do we get hold of those?
>
> 2.       Is this the right forum to ask such questions about
> certification? If not, please redirect to appropriate folks.
>
>
>
> Thanks
>
> Prakash
>
>
>
> *From:* Harsha Ramamurthy
> *Sent:* Monday, April 21, 2014 2:25 PM
> *To:* fuel-dev@xxxxxxxxxxxxxxxxxxx; jpipes@xxxxxxxxxxxx
> *Cc:* Prakash Kaligotla
> *Subject:* Query on Mirantis Openstack deployment
>
>
>
> Hi Folks,
>
>
>
> We are currently working on setting up an environment for certification of
> Brocade networking plugins by Mirantis. Our current plan is to use 1
> controller and 1 compute node but the model suggested in Mirantis
> documentation<http://docs.mirantis.com/fuel/fuel-4.1/pre-install-guide.html#preparing-the-mirantis-openstack-deployment>seems to be as below:
>
>
>
> [image: cid:image007.png@01CF5D6B.DE276000]
>
>
>
>
>
>
>
> For partner certification, is there a required/recommended deployment
> model that needs to be followed? Appreciate your inputs here. Thank you…
>
>
>
> Regards
>
> Harsha
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
45bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com <http://www.mirantis.ru/>
www.mirantis.ru
vkuklin@xxxxxxxxxxxx