Open Stack

Hi Swati,

It looks like you're doing well so far! In addition to my review feedback
via IRC, let me try to answer your questions.

The directory containing the files which hold the SHA's is here:
https://github.com/openstack/openstack-ansible/tree/master/playbooks/defaults/repo_packages

Considering that Designate is an OpenStack Service, the appropriate entries
should be added into this file:
https://github.com/openstack/openstack-ansible/blob/master/playbooks/defaults/repo_packages/openstack_services.yml

The order of the services is generally alphabetic, so Designate should be
added after Cinder and before Glance.

I'm not sure I understand your second question, but let me try and respond
with what I think you're asking. Assuming a running system with all the
other components, and an available container for Designate, the workflow
will be:

1 - you execute the os-designate-install.yml playbook.
2 - Ansible executes the pre-tasks, then the role at
https://github.com/sharmaswati6/designate_files/blob/master/playbooks/os-designate-install.yml#L64
3 - Ansible then executes
https://github.com/sharmaswati6/designate_files/blob/master/playbooks/roles/os_designate/tasks/main.yml
4 - Handlers are triggered when you notify them, for example:
https://github.com/sharmaswati6/designate_files/blob/master/playbooks/roles/os_designate/tasks/designate_post_install.yml#L54

Does that help you understand how the tasks and handlers are included for
execution? Does that answer your question?

With regards to creating a DB user & DB - as you've modeled the role from
Aodh, which doesn't use Galera, you're missing that part An example you can
model from is here:
https://github.com/openstack/openstack-ansible/blob/master/playbooks/roles/os_glance/tasks/glance_db_setup.yml

Question 4 is a complex one, and I don't know enough about Designate to
answer properly. From what I can see you're already doing the following in
the role:

1 - preparing the host/container, RabbitMQ (and soon will be doing the DB)
for a Designate deployment
2 - installing the apt and python packages required for Designate to be
able to run
3 - placing down the config files and upstart scripts for Designate to run
4 - registering the Designate service endpoint

Once that's done, I'm not entirely sure what else needs to be done to make
Designate do what it needs to do. At that point, are you able to see the
service in the Keystone service catalog? Can you interact with it via the
CLI?

A few housekeeping items relating to the use of email and the mailing list:

If you wish to gain the attention of particular communities on the
openstack-dev mailing list, the best is to tag the subject line. In this
particular case as you're targeting the OpenStack-Ansible community with
questions you should add '[openstack-ansible]' as a tag in your subject
line. If you were also targeting questions regarding Designate, or wish for
the Designate community to also be informed then similarly add
'[designate]' as a tag in the subject line.

Secondly, note that you're addressing a community of people. There's no
need to single anyone out and very definitely no need to address or CC our
email addresses. We're all members of the openstack-dev mailing list and
will all respond to you via the mailing list.

I'd appreciate it if you could respect these conventions from now on. It'll
help improve your experience in the OpenStack community.

Thanks,

Jesse
IRC: odyssey4me

On 16 December 2015 at 04:46, Sharma Swati6 <sharma.swati6 at tcs.com> wrote:

> Hi
> *Major, Jean, Jesse and Kevin,*
> I have added some part of *Designate* code and uploaded it on
> https://github.com/sharmaswati6/designate_files
>
> Could you please review this and help me in answering the following
> questions- <https://github.com/sharmaswati6/designate_files>
>
>    1. Is there some specific location for the server-side code for all
>    Openstack components? And whether I will downloading the actual designate
>    git code to the same location?
>    2. Is there some specific file where I have to give the reference for
>    "tasks:" and "handlers:", so that they can be called via roles.
>    3. To create Designate mysql database, is it reference to be given
>    somewhere?
>    4. How are the hooks(setup details) of a new component associated to
>    it in Openstack-Ansible. *Eg*- the setup details for Designate
>    http://git.openstack.org/cgit/openstack/designate/tree/setup.cfg?wb48617274=B56AA8FF
>    should map to which file in Openstack-Ansible structure?
>
> Thanks in advance.
> Regards,
> Swati Sharma
> System Engineer
> Tata Consultancy Services
> Gurgaon - 122 004,Haryana
> India
> Cell:- +91-9717238784
> Mailto: sharma.swati6 at tcs.com
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty. IT Services
> Business Solutions
> Consulting
> ____________________________________________
>
>
> -----Sharma Swati6/DEL/TCS wrote: -----
> To: major at mhtx.net, jean-philippe at evrard.me,
> jesse.pretorius at rackspace.co.uk, kevin.carter at rackspace.com
> From: Sharma Swati6/DEL/TCS
> Date: 12/08/2015 01:56PM
> Cc: openstack-dev at lists.openstack.org, Partha Datta/DEL/TCS at TCS,
> pandey.preeti1 at tcsin.com
> Subject: Regarding Designate install through Openstack-Ansible
>
> Hi *Major, Jean, Jesse and Kevin,*
>
> Hope you are all doing well.
>
> I have been interacting with you lately on openstack mailing lists and IRC
> chats regarding *Designate component inclusion in Openstack-Ansible*, so
> that its deployment can be made similar to other components.
>
> As recommended, I have opened a *spec* also at :
> https://review.openstack.org/#/c/254161/ and uploaded the sample
> *designate.yml* file at
> https://github.com/prpandey26/Designate/blob/master/designate.yml#L3.
>
> To proceed with the configuration and role setup, I have the following
> queries-
>
>    1. I believe for making the starting the initial setup, only conf.d
>    and env.d needs to be altered. *In env.d, I edited the designate.yml
>    file, then in conf.d, what host changes exactly I need to make for
>    designate component?*
>    2. Jean suggested that "after making changes in env.d and conf.d,
>    ansible will create the new entries for your component". *Do I have to
>    run anything for this? At what location will the new entries be created? Is
>    it with respect to the roles for designate automatically created?*
>    3. As a next step, I am planning to add role directories for designate
>    component *'os-designate-yml' file in
>    '/opt/openstack-ansible/playbooks'* and a seperate roles directory for *'os-designate'
>    at '/opt/openstack-ansible/playbooks/roles'.* *Can you please let me
>    know if this has to be created by us or env.d and conf.d will directly
>    created it?*
>
> I have not seen any document yet for the extra-containers to be added to
> openstack-ansible, however I checked only specs have been created for
> ironic, trove, etc.
>
> Hence, any help from you regarding the steps in sequence will be highly
> appreciated.
>
>
> Thanks & Regards
> Swati Sharma
> System Engineer
> Tata Consultancy Services
> Mailto: sharma.swati6 at tcs.com
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty. IT Services
> Business Solutions
> Consulting
> ____________________________________________
>
>
> -----Major Hayden <major at mhtx.net> wrote: -----
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> From: Major Hayden <major at mhtx.net>
> Date: 12/04/2015 06:53PM
> Subject: Re: [openstack-dev] [openstack-ansible] Install Openstack-Ansible
>
> On Fri, 2015-12-04 at 10:01 +0530, Sharma Swati6 wrote:
> > To add a new container, we have followed the steps as mentioned in
> > the extra_container.yml.example. Please find the sample designate.yml
> > file attached and created as per the steps.
>
> That's a good start.  However, you'll need to sign up[1] to be an
> OpenStack developer (agreeing to some contracts and things so you can
> commit this into the upstream repositories.
>
> Once you do that, you'll want to assemble a spec for the changes you
> want to make.  A spec defines what you hope to accomplish and gives
> everyone on the project a chance to review the steps you're planning to
> take.  You can look at a spec I wrote[2] for ideas and then use the
> openstack-ansible-specs template[3] to begin working on your spec.
>
> A spec isn't busywork -- it shows the intention of what you're trying
> to do and allows other people on the project to point out areas of
> concern and improvement.
>
> > To add the new roles in openstack-ansible repository, shall I create
> > the directory looking at what is there for keystone or other
> > components and make the configuration changes only, or can I clone it
> > from somewhere also?
>
> There is a push lately to use independent role repositories, but I'm
> not sure if that's a hard requirement at the moment.  Jesse Pretorius
> or Kevin Carter may be better people to talk about that in this thread.
>
> Details on independent role repositories are in a spec[4] as well.
>
> > Thereafter, as suggested by you, I have to test this new container
> > with the existing ones.
> >
> > I believe there is no such link available with such steps and 'how
> > to' part for openstack-ansible. Please let me know if you/anyone else
> > have already done this part to add a new component container
> > similarly.
>
> We can help you with this in IRC once you've completed the other steps
> I've listed above.  Join us on Freenode in #openstack-ansible and we
> will be happy to help you along the way!
>
> [1] http://docs.openstack.org/infra/manual/developers.html
> [2]
> http://specs.openstack.org/openstack/openstack-ansible-specs/specs/mitaka/security-hardening.html
> [3]
> https://github.com/openstack/openstack-ansible-specs/blob/master/specs/template.rst
> [4]
> http://specs.openstack.org/openstack/openstack-ansible-specs/specs/mitaka/independent-role-repositories.html
>
> --
> Major Hayden
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Jesse Pretorius
mobile: +44 7586 906045
email: jesse.pretorius at gmail.com
skype: jesse.pretorius
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151217/c57abccc/attachment.html>