Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

[j.kl...@cloudbau.de]

Hi Doug,

first of all sorry for the late response. I am the current PTL of the 
openstack-chef project and read the spec a while ago, but did not really 
connect it to our project. To be honest, i am not really sure what we would 
move and how to do it. Currently we have some wiki pages, but most of them are 
pretty old and completely outdated since we stopped caring for them after we 
dropped to only a few contributors and moved our focus to maintaining the 
project code itself.

Currently we own and maintain 12 service and ops cookbook repositories:

cookbook-openstack-block-storage
cookbook-openstack-common
cookbook-openstack-compute
cookbook-openstack-dashboard
cookbook-openstack-identity
cookbook-openstack-image
cookbook-openstack-integration-test
cookbook-openstack-network
cookbook-openstack-ops-database
cookbook-openstack-ops-messaging
cookbook-openstack-orchestration
cookbook-openstack-telemetry

one (not very often used) specs repository:

openstack-chef-specs

 and one repo to integrate them all:

openstack-chef-repo

All of these repos have some READMEs that contain some of the documentation 
needed to use these. The documentation on how to use the openstack-chef project 
as a combination of all these cookbooks, is located under 
https://github.com/openstack/openstack-chef-repo/tree/master/doc (which might 
already be close to the right space ?). Looking through the openstack-manuals 
repo, i did not find any documentation specific for our projects, so i think we 
do not need to export/import any of it. In my opinion the easiest way to follow 
the proposed change of us would be to just move the stuff we have under the 
‘openstack-chef-repo’ mentioned above and add some more files to follow the 
‘minimal layout’. If you agree on this, i can try to push a patch for it next 
week and add you as a reviewer?

Cheers,
Jan


On 23. June 2017 at 16:16:58, Doug Hellmann (d...@doughellmann.com) wrote:


On Jun 23, 2017, at 8:57 AM, Renat Akhmerov  wrote:

I can say for Mistral . We only planned to add Mistral docs to the central repo 
but didn’t do it yet. So, as far as I understand, we don’t need to move 
anything. We’ll review the spec and adjust the folder structure according to 
the proposed.

Please do review the steps in the spec. Not all of them are about moving 
content. There are steps for setting up the new build job so that the content 
will be published to the new URLs as well.

Doug


Thanks

Renat Akhmerov
@Nokia

23 июня 2017 г., 3:32 +0700, Doug Hellmann , писал:
Excerpts from Alexandra Settle's message of 2017-06-08 15:17:34 +:
Hi everyone,

Doug and I have written up a spec following on from the conversation [0] that 
we had regarding the documentation publishing future.

Please take the time out of your day to review the spec as this affects 
*everyone*.

See: https://review.openstack.org/#/c/472275/

I will be PTO from the 9th – 19th of June. If you have any pressing concerns, 
please email me and I will get back to you as soon as I can, or, email Doug 
Hellmann and hopefully he will be able to assist you.

Thanks,

Alex

[0] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117162.html

Andreas pointed out that the new documentation job will behave a
little differently from the old setup, and thought I should mention
it so that people aren't surprised.

The new job is configured to update the docs for all repos every
time a patch is merged, not just when we tag releases. The server
projects have been working that way, but this is different for some
of the libraries, especially the clients.

I will be going back and adding a step to build the docs when we
tag releases after the move actually starts, so that we can link
to docs for specific versions of projects. That change will be
transparent to everyone else, so I have it on the list for after
the migration is under way.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [all][deployment] Deployment Working Group (DWG)

[j.kl...@cloudbau.de]

+1 and big thanks for bringing this up!

OpenStack Chef will most likely use Ansible as an orchestrator for multi node 
deployments in the near future and i love the idea about sharing “common 
configuration options”.

Cheers,
Jan
On 14 March 2017 at 21:39:19, Emilien Macchi (emil...@redhat.com) wrote:

OpenStack community has been a welcoming place for Deployment tools.  
They bring great value to OpenStack because most of them are used to  
deploy OpenStack in production, versus a development environment.  

Over the last few years, deployment tools project have been trying  
to solve similar challenges. Recently we've seen some desire to  
collaborate, work on common topics and resolve issues seen by all  
these tools.  

Some examples of collaboration:  

* OpenStack Ansible and Puppet OpenStack have been collaborating on  
Continuous Integration scenarios but also on Nova upgrades orchestration.  
* TripleO and Kolla share the same tool for container builds.  
* TripleO and Fuel share the same Puppet OpenStack modules.  
* OpenStack and Kubernetes are interested in collaborating on configuration  
management.  
* Most of tools want to collect OpenStack parameters for configuration  
management in a common fashion.  
* [more]  

The big tent helped to make these projects part of OpenStack, but no official  
group was created to share common problems across tools until now.  

During the Atlanta Project Team Gathering in 2017 [1], most of current active  
deployment tools project team leaders met in a room and decided to start actual 
 
collaboration on different topics.  
This resolution is a first iteration of creating a new working group  
for Deployment Tools.  

The mission of the Deployment Working Group would be the following::  

To collaborate on best practices for deploying and configuring OpenStack  
in production environments.  


Note: in some cases, some challenges will be solved by adopting a technology  
or a tool. But sometimes, it won't happen because of the deployment tool  
background. This group would have to figure out how we can increase  
this adoption and converge to the same technologies eventually.  


For now, we'll use the wiki to document how we work together:  
https://wiki.openstack.org/wiki/Deployment  

The etherpad presented in [1] might be transformed in a Wiki page if  
needed but for now we expect people to update it.  

[1] https://etherpad.openstack.org/p/deployment-pike  


Let's make OpenStack deployments better and together ;-)  
Thanks,  
--  
Emilien Macchi  

__  
OpenStack Development Mailing List (not for usage questions)  
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe  
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev  
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] Discount codes for ATCs

[j.kl...@cloudbau.de]

Hi,

i just received a discount code for the Boston summit as an ATC for 300$ (while 
the ticket price is currently at 600$). As far as i know every ATC who went to 
the PTG received a discount code of 600$ (also stated here 
https://www.openstack.org/summit/boston-2017/faq/). So how should i take this? 
ATCs who can afford to travel to the PTG receive more discount/funding from the 
foundation than ATCs who can not afford to go there? I am pretty sad about the 
direction we seem to move with this and am hoping that this will only be true 
for the Boston summit.

Cheers,
Jan

PS: Probably someone also wants to change the FAQ text here 
(https://www.openstack.org/summit/boston-2017/faq/) which states: 'No “ATC” 
codes will be distributed for the Boston Summit.”__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [chef] release of stable/newton cookbook set

[j.kl...@cloudbau.de]

Hi,

i just wanted to let you all know that we recently released the stable/newton 
cookbook set.

For this cycle the released cookbook set includes:

cookbook-openstack-block-storage (deploying cinder)
cookbook-openstack-common (shared configuration and libraries)
cookbook-openstack-compute (deploying nova)
cookbook-openstack-dashboard (deploying horizon)
cookbook-openstack-identity (deploying keystone)
cookbook-openstack-image (deploying glance)
cookbook-openstack-integration-test (deploying tempest)
cookbook-openstack-network (deploying neutron)
cookbook-openstack-ops-database (shared database configuration)
cookbook-openstack-ops-messaging (shared mq configuration)
cookbook-openstack-orchestration (deploying heat)
cookbook-openstack-telemetry (deploying ceilometer and gnocchi)
openstack-chef-repo (combining all cookbooks and deployment specific 
configuration)

Sadly we were not able to release the cookbook-openstack-application-catalog 
(deploying Murano) this cycle, since we decided the deployment and the provided 
packages are not stable enough. We are however planning to release it with the 
stable/ocata cookbook set, but would be more than happy to get some support and 
more hands for the development and stabilisation of this.
During the ocata development cycle we are planning to add the compute 
placement-api and back port it also to stable/newton if possible. Additionally 
we will try to move as many projects as possible to be run via WSGI (as stated 
in our pike community goals).
Since we are currently down to only three core reviewers and not many more code 
contributors, we will reduce the efforts of adding new features to a minimum 
and focus on stabilisation and the minimal need feature set for ocata. If you 
would like to add a feature or even a whole project cookbook, please ping me or 
any other core in our irc channel or via this mailing list.

I will also be available during the OpenStack Ops Mid-cycle Meetup in Milan 
this month and will moderate the ops-config-management session (which of course 
will also be about all the other config management tools).

Cheers,
Jan__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [chef] draft logo & sneak peek

[j.kl...@cloudbau.de]

Hi,

I think the logo is nice, but it should not just say "Chef" below it, since
that is just the company name of the software vendor, but not our project
name. I think our project name is "ChefOpenStack" or "openstack-chef" or
"chef-openstack", depending where you look. I think we should figure that
out and clarify before they go to print.

Cheers,
Jan
On Tue, 25 Oct 2016 at 07:28, Samuel Cassiba  wrote:

> Ohai Chefs,
>
> Here is the draft of our project logo. As you may remember, we requested a
> kangaroo some time ago to resemble the Xzibit meme-like way of how we
> deploy OpenStack, and this is the draft of that decision. I have enclosed
> the original message, which includes a link for feedback.
>
> Since neither myself nor the other cores will be at the PTG, we’ll have to
> work out some way to get the final product distributed if interested.
>
> Have a great Summit!
>
> Best,
> Samuel Cassiba
> Project Team Lead, OpenStack Chef
>
> Begin forwarded message:
>
> *From: *Heidi Joy Tretheway 
> *Subject: **Your draft logo & sneak peek*
> *Date: *October 21, 2016 at 10:12:54 PDT
> *To: *Samuel Cassiba 
>
> Hi,
>
> We're excited to show you the draft version of your project logo,
> attached. We want to give you and your team a chance to see the mascot
> illustrations before we make them official, so we decided to make Barcelona
> the draft target, with final logos ready by the Project Team Gathering in
> Atlanta in February.
>
> Our illustrators worked as fast as possible to draft nearly 60 logos, and
> we're thrilled to see how they work as a family. Here's a 50-second "sneak
> peek" at how they came together: https://youtu.be/JmMTCWyY8Y4
>
> We welcome you to *share this logo with your team and discuss it in
> Barcelona*. We're very happy to take feedback on it if we've missed the
> mark. The style of the logos is consistent across projects, and we did our
> best to incorporate any special requests, such as an element of an animal
> that is especially important, or a reference to an old logo.
>
>
> We ask that you don't start using this logo now since it's a draft. Here's 
> *what
> you can expect for the final product*:
>
>- A horizontal version of the logo, including your mascot, project
>name and the words "An OpenStack Community project"
>- A square(ish) version of the logo, including all of the above
>- A mascot-only version of the logo
>- Stickers for all project teams distributed at the PTG
>- One piece of swag that incorporates all project mascots, such as a
>deck of playing cards, distributed at the PTG
>- All digital files will be available through the website
>
>
> We know this is a busy time for you, so to take some of the burden of
> coordinating feedback off you, we made a feedback form*:*
> http://tinyurl.com/OSmascot  You are also welcome to reach out to Heidi
> Joy directly with questions or concerns. Please provide *feedback by
> Friday, Nov. 11*, so that we can request revisions from the illustrators
> if needed. Or, if this logo looks great, just reply to this email and you
> don't need to take any further action.
>
> Thank you!
> Heidi Joy Tretheway - project lead
> Todd Morey - creative lead
>
> P.S. Here's an email that you can copy/paste to send to your team
> (remember to attach your logo from my email):
>
> Hi team,
> I just received a draft version of our project logo, using the mascot we
> selected together. A final version (and some cool swag) will be ready for
> us before the Project Team Gathering in February. Before they make our logo
> final, they want to be sure we're happy with our mascot.
>
> We can discuss any concerns in Barcelona and you can also provide direct
> feedback to the designers: http://tinyurl.com/OSmascot  Logo feedback is
> due Friday, Nov. 11. To get a sense of how ours stacks up to others, check
> out this sneak preview of several dozen draft logos from our community:
> https://youtu.be/JmMTCWyY8Y4
>
>
> [image: photo]
> *Heidi Joy Tretheway*
> Senior Marketing Manager, OpenStack Foundation
> 503 816 9769 | Skype: heidi.tretheway
> 
> 
>   
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [chef] Adding calbers to openstack-chef-core

[j.kl...@cloudbau.de]

Hi,

sounds good, +1 from me.

Cheers,
Jan

> On 05 Oct 2016, at 05:44, Samuel Cassiba  wrote:
> 
> Ohai Chefs!
> 
> I would like to nominate Christoph Albers (irc: calbers) for
> openstack-chef-core.
> 
> Christoph has consistently provided great quality reviews over the
> Newton cycle. He has been instrumental in getting the cookbooks up to
> speed with Identity v3 and openstackclient. During Mitaka, his reviews
> were crucial to the refactor work that took place during that cycle.
> From the quality of his reviews, he has a solid understanding of the
> codebase and I think he is qualified to be a core reviewer.
> 
> This will bring us back up to three dedicated core reviewers, and I
> would like to reimplement a 2x +2 policy for changes.
> 
> If there are no objections, I will put in a change at the end of the
> week. Consider this a +1 vote from me.
> 
> Thanks,
> 
> -sc
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] cross-project deployment tool meeting

[j.kl...@cloudbau.de]

Hi,

Currently three people participated in the doodle and I think we can start with 
that and not wait for more. Judging from the result all three of us should be 
available today at 16 UTC to 17 UTC. Please let me know if this is accurate and 
if you want to attend today. I would suggest we meet in one of the deployment 
tool irc channels and have a short chat about how to continue.

Cheers,
Jan

> On 09 May 2016, at 09:14, "j.kl...@cloudbau.de" <j.kl...@cloudbau.de> wrote:
> 
> Hi,
> 
> I have created a doodle so we can find a slot for our first meeting. Please 
> respond until this Friday so I can try an secure a spot in the cross project 
> irc room.
> 
> https://doodle.com/poll/7wrmtpc4ffcwi428
> 
> Cheers,
> Jan
> 
> Sent from my mobile 
> 
>> On 06 May 2016, at 22:13, Emilien Macchi <emil...@redhat.com> wrote:
>> 
>> I started https://etherpad.openstack.org/p/deployment-tools-wg
>> Recent threads on openstack-dev shows that we need to work together
>> (xenial things, etc).
>> 
>> If you represent an OpenStack deployment tool (Chef, Ansible, etc),
>> please add your name and your TZ in the etherpad.
>> Also feel free to bring topics, so we can start a bi-monthly meeting
>> (maybe less/more?) and work together.
>> 
>> Thanks and enjoy WE.
>> 
>> On Fri, May 6, 2016 at 3:51 PM, Jesse Pretorius
>> <jesse.pretor...@gmail.com> wrote:
>>> On 26 April 2016 at 17:54, Jan Klare <j.kl...@cloudbau.de> wrote:
>>>> 
>>>> 
>>>> i just wanted to follow up on this session
>>>> (https://etherpad.openstack.org/p/newton-deployment-tools-discussion) were
>>>> we talked about a cross-project meeting for deployment tools. I would love
>>>> to see something like that happen and it would be great if we can find a
>>>> specific date (maybe monthly) to do something like that. If you are
>>>> interested in going to such a meeting, please reply to this mail with a
>>>> suggestion when you could join such a meeting.
>>>> 
>>>> Cheers,
>>>> Jan (OpenStack Chef)
>>> 
>>> 
>>> Thanks Jan. I think once per month will be enough.
>>> 
>>> I'm based in the UK and am reasonably flexible around times, although it is
>>> usually more productive if it can be held during my day rather than my
>>> evening.
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> 
>> -- 
>> Emilien Macchi
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] cross-project deployment tool meeting

[j.kl...@cloudbau.de]

Hi,

I have created a doodle so we can find a slot for our first meeting. Please 
respond until this Friday so I can try an secure a spot in the cross project 
irc room.

https://doodle.com/poll/7wrmtpc4ffcwi428

Cheers,
Jan

Sent from my mobile 

> On 06 May 2016, at 22:13, Emilien Macchi <emil...@redhat.com> wrote:
> 
> I started https://etherpad.openstack.org/p/deployment-tools-wg
> Recent threads on openstack-dev shows that we need to work together
> (xenial things, etc).
> 
> If you represent an OpenStack deployment tool (Chef, Ansible, etc),
> please add your name and your TZ in the etherpad.
> Also feel free to bring topics, so we can start a bi-monthly meeting
> (maybe less/more?) and work together.
> 
> Thanks and enjoy WE.
> 
> On Fri, May 6, 2016 at 3:51 PM, Jesse Pretorius
> <jesse.pretor...@gmail.com> wrote:
>> On 26 April 2016 at 17:54, Jan Klare <j.kl...@cloudbau.de> wrote:
>>> 
>>> 
>>> i just wanted to follow up on this session
>>> (https://etherpad.openstack.org/p/newton-deployment-tools-discussion) were
>>> we talked about a cross-project meeting for deployment tools. I would love
>>> to see something like that happen and it would be great if we can find a
>>> specific date (maybe monthly) to do something like that. If you are
>>> interested in going to such a meeting, please reply to this mail with a
>>> suggestion when you could join such a meeting.
>>> 
>>> Cheers,
>>> Jan (OpenStack Chef)
>> 
>> 
>> Thanks Jan. I think once per month will be enough.
>> 
>> I'm based in the UK and am reasonably flexible around times, although it is
>> usually more productive if it can be held during my day rather than my
>> evening.
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> -- 
> Emilien Macchi
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev