Re: [Openstack-operators] Draft Agenda for MAN Ops Meetup (Feb 15, 16)

accurate! There was a huge intersection there so it became one thing. Rocky that's awesome, and I wish I could be there! - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools -

Re: [Openstack-operators] [osops] 2016-01-27 meeting?

if there's interest from the operator community to start talking about > this. Sounds great, go ahead and add it to the etherpad[1]. > [1]:https://etherpad.openstack.org/p/osops-irc-meeting-20160127 Till tomorrow! - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -

Re: [Openstack-operators] ATC status for OSOps contribution

story short, we've been pushing to make OSOps ATC eligible but it won't happen till we have "enough involvement" which is up to the TC. The ultimate goal is ATC, but it's still at least one or two releases down the line. :( - -- Best Regards, JJ Asghar c: 512.619.0722 t:

Re: [Openstack-operators] [openstack-operators] 2016-01-13 OSOps meeting notes

e ASAP. Sorry to everyone who has been confused by this, I take full responsibility for messing up that review for eavesdrop[1]. [1]: http://eavesdrop.openstack.org/#OpenStack_OSOps/Monitoring_and_Tools_Working_Group - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNAT

[Openstack-operators] [openstack-operators] 2016-01-13 OSOps meeting notes

rs_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-01-13-19.00.html [2]: http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-01-13-19.00.log.html - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP

[Openstack-operators] [openstack-operators] OpenStack Board of Directors 2016

r time and consideration. [1]: http://bit.ly/JJ-4-OpenStack-BoD-2016 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWlCqeAAoJEDZbxzMH0+jTxJAP/0WpmO0dIhgDtH

[Openstack-operators] [openstack][openstack-dev][openstack-operators] Starting with Jenkins and jjb/OpenStack Board of Directors

r time, and if you have any questions don't hesitate to reach out. [1]: http://jjasghar.github.io/blog/2016/01/03/getting-jenkins-and-jenkins-job-builder-running/ [2]: http://bit.ly/JJ-4-OpenStack-BoD-2016 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNAT

Re: [Openstack-operators] 2015-12-30 Meeting

can allot time for everyone. Specifically our next meeting is: 2016-01-13[3] at 1900UTC. [1]: https://wiki.openstack.org/wiki/Osops [2]: https://wiki.openstack.org/wiki/Osops/Osops-agenda [3]: https://etherpad.openstack.org/p/osops-irc-meeting-2016113 - -- Best Regards, JJ Asghar c: 512.619.072

[Openstack-operators] [openstack-operators] 2015-12-30 Meeting

great New Years, and see you 2016-01-13[2]. [1]: https://etherpad.openstack.org/p/osops-irc-meeting-20151230 [2]: https://etherpad.openstack.org/p/osops-irc-meeting-20106113 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Co

[Openstack-operators] [openstack-operators] OSOps tools-contrib to tools-generic diagram

x27;d love some feedback and thoughts on this, so please don't hesitate to comment on it. :) [1]: https://wiki.openstack.org/wiki/Osops [2]: https://wiki.openstack.org/wiki/Osops#Overview_moving_code - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATU

[Openstack-operators] [openstack-operators][osops] 2015-12-16 Meeting Notes

.00.txt [3]: http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-12-16-19.00.log.html [4]: https://etherpad.openstack.org/p/osops-irc-meeting-20151230 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP

[Openstack-operators] [openstack][openstack-dev][openstack-operators][chef] kitchen-openstack 2.2.0 released!

stack/blob/master/CHANGELOG.md#220 [3]: https://github.com/test-kitchen/kitchen-openstack/issues - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWcbXfAAoJEDZbxz

[Openstack-operators] [openstack-operators][osops] Meeting Tomorrow!

s-irc-meeting-20151216 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWcKl8AAoJEDZbxzMH0+jT+KgP/RTvm85h2eKr5z+YmAI

Re: [Openstack-operators] OpenStack Liberty automation script release.

] process to get the it up on review.openstack.org [1]: https://github.com/openstack/osops-tools-contrib [2]: http://docs.openstack.org/infra/manual/developers.html - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GP

Re: [Openstack-operators] Could we release osops-tools-monitoring ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/7/15 2:56 PM, Emilien Macchi wrote: > On 12/07/2015 11:37 AM, JJ Asghar wrote: >> On 12/7/15 6:45 AM, Emilien Macchi wrote: >> Can you link me the RDO release process/strategies? Do they just release >> on X.y.z releases?

Re: [Openstack-operators] Could we release osops-tools-monitoring ?

or our next meeting[1]. I'm like to defer to the group here, should we have releases? [1]: https://etherpad.openstack.org/p/osops-irc-meeting-20151216 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTo

[Openstack-operators] [ososp] Operators OSOps Monitoring/Tools Working Group - Meeting Notes (12/02/2015)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Meeting Notes - 11/18/2015 - 1900 UTC IRC Room: #openstack-meeting-4 Attendees: * j^2 (87) * mriedem (78) * balajin (32) * klindgren (29) * xavpaice (19) * openstack (3) * Bjoern_ (1) * BjoernT (1) * ctina (1) * serverascode (1) # Agenda Topics Pre

[Openstack-operators] [openstack-operators][osops] Meeting in about an hour

51202 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWXzQhAAoJEDZbxzMH0+jTJcoP/izRY4dYfZOGHZoBTFBHg0v8 sqViFf/Ee3QSBcNBeot2Se+459FNHwv6hlNJ1OLteyIZLMBF3j3IsaSiaIG

Re: [Openstack-operators] OpenStack Consult Opp (Network/Horizon/VNC)

b-related > mailing list if that could be setup? > > > On Tue, Nov 24, 2015 at 12:51 PM, JJ Asghar <mailto:j...@chef.io>> wrote: > > > As another place, other than the job posting site I just created > this review[1]. > > If you like this idea please +1 it.

Re: [Openstack-operators] OpenStack Consult Opp (Network/Horizon/VNC)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/24/15 2:41 PM, JJ Asghar wrote > > I think this brings in the conversation, where _should_ these types > of emails be sent? > > Maybe we should create a [openstack-jobs] list? So there is a one > stop shop that we can po

Re: [Openstack-operators] OpenStack Consult Opp (Network/Horizon/VNC)

ly and guaranteed we will make it worth your while. ; ) I think this brings in the conversation, where _should_ these types of emails be sent? Maybe we should create a [openstack-jobs] list? So there is a one stop shop that we can point these types of requests to? - -- Best Regards, JJ Asgha

Re: [Openstack-operators] Operational Director?

more updates when the email is posted. - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWVMrCAAoJEDZbxzMH0+jTa9kP/i7chPhS++tBz78yalNVYj02 30GvIuQtGJaGpFNS0xoc5UlSaM9mYm2+

Re: [Openstack-operators] Operational Director?

hought of. If I get the seat I'll be the best representation for our community possible. It's great that we are stepping up and making our voices heard. - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2

Re: [Openstack-operators] Moving monitoring-for-openstack to osops

ing them? It looks like we're going pep8 for bash/python, and then our .rubocop.yml[2] is going to be taken from the chef mysql cookbook. [1]: https://wiki.openstack.org/wiki/Osops [2]: https://github.com/chef-cookbooks/mysql/blob/master/.rubocop.yml - -- Best Regards, JJ Asghar c:

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib is open for business!

lts to Apache2, unless stated otherwise in the code. In order to get to osops-tools-generic, you MUST have a license stated in the code and go to the coding standards that we have decided on. - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version:

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib is open for business!

ting the README to state "Your > code will be licensed under Apache 2 unless you mention otherwise." > I love this idea. I saw the review come in, we should get that merged ASAP. - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Ver

Re: [Openstack-operators] How to install magnum?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/3/15 11:48 AM, Mike Perez wrote: > On 18:51 Oct 28, Mike Perez wrote: >> On 12:35 Oct 28, JJ Asghar wrote: >>> On 10/28/15 10:35 AM, Mike Perez wrote: >>>> On 14:09 Oct 16, hittang wrote: >>>>

[Openstack-operators] [openstack][openstack-operators][openstack-dev] IRC meeting(s)

in some good working practices. I'd love to talk about this more, so please don't hesitate to reach out. [1]: http://jjasghar.github.io/blog/2015/11/18/characteristics-of-a-successful-chatroom-meeting/ - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATU

[Openstack-operators] [openstack-operators][osops] tools-contrib is open for business!

lob/master/README.rst - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWTO+/AAoJEDZbxzMH0+jTRxQQAK2DJdCTnihR7Y

[Openstack-operators] [openstack-operators][osops] Agendas and Whatnot

op.openstack.org/meetings/operators_ops_tools_monitoring/2015/operators_ops_tools_monitoring.2015-11-18-19.00.log.html [2]: https://wiki.openstack.org/wiki/Osops/Osops-agenda - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2

Re: [Openstack-operators] OPs Midcycle location discussion.

the harsh reality of it is that no matter what we do they will still miss out on some of the conversations. - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWS4suAA

Re: [Openstack-operators] [openstack-operators][osops][tools-generic] Coding Standards/Coding Linters for tools-generic

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/16/15 7:43 PM, Clayton O'Neill wrote: > I think it’s a good idea. I think scripts and such that don’t pass the > listing tools can go into the contrib repos and if they get cleaned up > then they can move over to the regular ones. Yep! That

[Openstack-operators] [openstack-operators][osops][tools-generic] Coding Standards/Coding Linters for tools-generic

ons, thoughts don't hesitate to reach out. [1]: https://review.openstack.org/#/c/229029 [2]: https://github.com/openstack-dev/bashate [3]: https://etherpad.openstack.org/p/osops-coding-standards - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNAT

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib repo review in

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > On 11/12/15 11:34 AM, JJ Asghar wrote: > Just a heads up, it's been merged.[1] I'll put together a wiki page > today on what the repo is for and why our community would want to use > it. I'll post again here when I

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib repo review in

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/12/15 11:34 AM, JJ Asghar wrote: > Hey everyone! > > Per our discussions in Tokyo, I have put the review[1] for the > "tool-contrib" repo. This will the a place for any script/tool can > go before being cur

Re: [Openstack-operators] [openstack-operators][osops] tools-contrib repo review in

but it's a trade off. I think when someone wants to be "curated" and we have decided on our criteria then they would remove it from one repo and add it to the other? This is something we should iron out sooner then later. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 --

[Openstack-operators] [openstack-operators][osops] tools-contrib repo review in

ghts don't hesitate to reach out. [1]: https://review.openstack.org/244783 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWRM2MAAoJEDZbxzMH0+jTCBEP/jW06eno4fCx/E

Re: [Openstack-operators] Error: Actor Crashed

me help, don't hesitate to come round to #openstack-chef and ping me (j^2) or just ask the question. We are usually always around. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 ___ OpenStack-operators mailing list OpenStack-operators

Re: [Openstack-operators] How to install magnum?

uot;prod" environment seems confusing at best. I've attempted a couple times now, and failed each one. I'm more then willing to help debug/QA the docs that yall decide to put together. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SI

Re: [Openstack-operators] [openstack-operators] OSOps we have a room in Toyko!

s and help share common pitfalls in any scale of their cloud. Anyone interested in running an OpenStack cloud should consider watching the OSOps project. Lauren, thanks! Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 ___ OpenStack-

Re: [Openstack-operators] [openstack-operators] OSOps we have a room in Toyko!

etherpad is: https://etherpad.openstack.org/p/osops-toyko-2015 Thanks! Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWJqHwAAoJEDZbxzMH0+jTIdcP/3OqHY

[Openstack-operators] [openstack-operators] OSOps we have a room in Toyko!

e can make sure we hit everything that we need to. [1]: https://mitakadesignsummit.sched.org/event/25d0acfd326696198af1e209a3671d1f#.ViZv8JdgjXo [2]: https://etherpad.openstack.org/p/osops-toyko-2015 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE---

Re: [Openstack-operators] Tokyo Ops Design Summit Tracks - Agenda on Sched

On 10/12/15 7:21 PM, Tom Fifield wrote: > On 13/10/15 06:01, JJ Asghar wrote: >> >> >> Tom, any chance we can get a "working session" for OSOps? I think some >> face to face time to start bootstrapping'll would be awesome. >> >> (I'

Re: [Openstack-operators] Tokyo Ops Design Summit Tracks - Agenda on Sched

On 10/12/15 3:51 PM, Christopher Aedo wrote: > On Sun, Oct 11, 2015 at 8:55 PM, Tom Fifield wrote: >> Hi all, >> >> We are still lacking: >> >> * Moderator(s) for Quotas and Billing >> * Content for about 3 slots. >> >> If you have interest for any of this, please speak now - time is running >>

Re: [Openstack-operators] Tokyo Ops Design Summit Tracks - Agenda on Sched

On 10/11/15 8:55 PM, Tom Fifield wrote: > Hi all, > > We are still lacking: > > * Moderator(s) for Quotas and Billing > * Content for about 3 slots. > > If you have interest for any of this, please speak now - time is running > out! > Tom, any chance we can get a "working session" for OSOps?

Re: [Openstack-operators] [OpenStack-docs][Neutron] Networking Guide - Call for contributors

this out. Has that idea gone? If not, I'll be evangelizing it in Tokyo ;). > > I am really looking forward to increase the contributors in this guide. Same here, we need to get this guide in order. - -JJ Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP S

Re: [Openstack-operators] [ops] Operator Local Patches

Just spit balling here But wouldn't the way you deploy/patch these patches be good for the OSOps tools? I bet there is some overlap and having a discussion around how to get those patches _out_ would be a good topic? (Probably for the Tools WG, but worth mentioning here) Best Regards

Re: [Openstack-operators] [openstack-operators][osops] Something other than NOOP in our jenkins tests

Seems solid Joe! Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 On 9/29/15 3:47 PM, Joe Topjian wrote: > +1 > > I like that idea. I think it also ties in nicely with both the > Monitoring and Tools WGs. > > Some projects have a directory called "

Re: [Openstack-operators] [openstack-operators][osops] Something other than NOOP in our jenkins tests

Seems reasonable. If someone could put a "dumping ground" directory together that would help. (with an uncurated script as an example) So, i'm getting a feeling we should roll back the bashscript gate, and go back to noop. Thoughts? Best Regards, JJ Asghar c: 512.619.0722 t: @

Re: [Openstack-operators] [openstack-operators][osops] Something other than NOOP in our jenkins tests

Awesome! That works! Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 On 9/29/15 1:27 PM, Christian Berendt wrote: > On 09/29/2015 07:45 PM, JJ Asghar wrote: >> So this popped up today[1]. This seems like something that should be >> leveraged in our gates/val

[Openstack-operators] [openstack-operators][osops] Something other than NOOP in our jenkins tests

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey All! So this popped up today[1]. This seems like something that should be leveraged in our gates/validations? Any thoughts? [1]: https://review.openstack.org/#/c/229046 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2

[Openstack-operators] [openstack-operators][osops] First contribution

you have something that can fit please don't hesitate to commit! Everyone please take a moment for David to thank him for getting the ball rolling! [1]: https://review.openstack.org/228545 [2]: https://review.openstack.org/228534 - -JJ - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jja

Re: [Openstack-operators] [Tools/Monitoring] New Time submitted and approved

well and we have a template[2] here too. Thoughts? [1]: http://bit.ly/os-chef-meeting-agendas [2]: https://etherpad.openstack.org/p/openstack-chef-meeting-template Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GP

Re: [Openstack-operators] [openstack-operators][osops] It's alive!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Awesome. This is great. I could try to find it, but can you link me to the agenda? There's a couple things I'd like to ask and look for some consensus so we can continue moving the framework forward. Best Regards, JJ Asghar c: 512.

[Openstack-operators] [openstack-operators][osops] It's alive!

[4]: https://bugs.launchpad.net/osops [5]: https://wiki.openstack.org/wiki/Osops - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJV+a03AAoJEDZbxzMH0+jTde0P/0CXmdzNv029R9

Re: [Openstack-operators] [openstack-operators] Announcement! We have everything ready to get to Stackforge!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 9/2/15 2:21 PM, JJ Asghar wrote: > > I've put the review[1] and it looks like it's pretty good. I'd like to announce it has been merged! > > I've created a launchpad[2] with both answers[3] and bugs[4] t

[Openstack-operators] [openstack-dev][openstack-operators][chef] Pre-release of new kitchen-openstack driver, Windows and 1.4 test-kitchen support

n/kitchen-openstack [3]: https://github.com/test-kitchen/kitchen-openstack/issues [4]: https://github.com/test-kitchen/kitchen-openstack#usage - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: G

[Openstack-operators] [openstack-operators] Announcement! We have everything ready to get to Stackforge!

launchpad.net/osops [3]: https://answers.launchpad.net/osops [4]: https://bugs.launchpad.net/osops [5]: https://wiki.openstack.org/wiki/Osops Oh! If yall can +1 the review to say you're in favor for this that would be amazing. The more support we get the more momentum we can get! Best Regards, JJ Asghar c:

Re: [Openstack-operators] [openstack-operators] Announcement! We are starting the Stackforge process!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I should mention I have created the Launchpad[1] also. I did put the maintainer as OpenStack Admins which i read incorrectly in the docs, so I'm in the process of fixing this. [1]: https://launchpad.net/osops Best Regards, JJ Asg

[Openstack-operators] [openstack-operators] Announcement! We are starting the Stackforge process!

://github.com/osops [2]: https://review.openstack.org/219760 - -JJ - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJV5x7fAAoJEDZbxzMH0+jT1yQP/AuyqvZCWaAJXaYg/tuCIVcf

[Openstack-operators] [openstack][openstack-dev][openstack-operators][chef] stable/kilo is born!

ng US business hours. [1]: https://wiki.openstack.org/wiki/Meetings/ChefCookbook Cheers! - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJV36LqAAoJEDZbxzMH0+jT1OAQAK6p

Re: [Openstack-operators] Draft Agenda for PAO Ops Meetup (August18, 19)

use something like zoom.us for any level of consistent two way connection. Granted from what I understand Youtube has a better track record, so in theory you could do the OnAir Hangout and they could at least consistently stream it. Just a friendly heads up. :) Best Regards, JJ Asghar c:

Re: [Openstack-operators] Draft Agenda for PAO Ops Meetup (August 18, 19)

how different operators check the health of their clouds seems like everyone could benefit. This is a topic veteran and beginner Operators can learn from and contribute to, even if there is a chance that we just rehash the same things over and over. > > On Mon, Aug 3, 2015 at 9:49 AM, JJ A

Re: [Openstack-operators] Draft Agenda for PAO Ops Meetup (August 18, 19)

0 - 16:00 Breakout Reports > > > > 16:00 - 17:00 Feedback Session, Tokyo Planning > > > > > > > There will be a followup email shortly regarding moderators for the > sessions - thanks to t

Re: [Openstack-operators] Chef cookbook

't done it yet, i strongly suggest here[2] it'll walk you through your questions about getting cookbooks onto your nodes and leveraging them there. [1]: https://github.com/chef/knife-openstack [2]: http://learn.chef.io/ Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2

[Openstack-operators] [openstack-operators][openstack-dev][chef] Pre-Release of knife-openstack is out (1.3.0.rc.1)

> > On Jun 25, 2015, at 2:58 PM, JJ Asghar wrote: > > I have released the 1.3.0.rc.0 version of the knife-openstack[1] gem. I have bumped the rc.1 and pushed the gem to rubygems.org. I added the initial floating_ip ability to list the floating_ip(s) from the knife plugin. We sh

[Openstack-operators] [openstack-operators][openstack-dev][chef] Pre-Release of knife-openstack is out (1.3.0.rc.0)

I have released the 1.3.0.rc.0 version of the knife-openstack[1] gem. If you find any uses or have questions don’t hesitate to email me directly or put an issue[2] in. We are planning on waiting for the floating-ip issue[3] to be resolved before the official release happens. [1]: https://ruby

Re: [Openstack-operators] openstack-announce gets in Junk/SPAM mail @outlook.com

> On Jun 24, 2015, at 7:00 AM, Lukas Lehner wrote: > > Hi > > I subscribed to openstack-announce with my Microsoft account. Most (90%) of > the mails go to Junk/SPAM folder. > > I clicked about 20 times the button "not junk". But still the same. > > http://i.imgur.com/ZI02VGx.png

[Openstack-operators] [openstack-operators][openstack-dev][chef] Release of knife-openstack is out (1.2.0)

I have released the 1.2.0 version of the knife-openstack[1] gem. If you find any uses or have questions don’t hesitate to email me directly or put an issue[2] in. [1]: https://rubygems.org/gems/knife-openstack [2]: https://github.com/chef/knife-openst

Re: [Openstack-operators] [openstack-operators][openstack-dev][openstack][chef] Pre-release of knife-openstack is out (1.2.0.rc1)

> On Jun 4, 2015, at 6:12 PM, JJ Asghar wrote: > > I have cut a new release of the knife-openstack[1] gem today. We have a > couple new features[2] which has been asked for a while. I have pushed another pre-release (1.2.0.rc2) of knife-openstack. The main change is sup

[Openstack-operators] [openstack-operators][openstack-dev][openstack][chef] Pre-release of knife-openstack is out (1.2.0.rc1)

Hey everyone! I have cut a new release of the knife-openstack[1] gem today. We have a couple new features[2] which has been asked for a while. If you would like to give it a shot and report back any issues you might find[3]. gem install knife-openstack --pre I’m hoping to give this a week or

[Openstack-operators] [openstack-dev][openstack-operators][chef] Thanks again, and we've already made amazing progress since Summit!

All, I’d like to thank everyone that came to the Vancouver Summit and our Official Ops Meeting[1]. Since then we have officially been sanctioned[2] and made amazing progress with true integration testing our cookbooks[3][4], including leveraging Rally[5] for benchmarking. Turns out after th

[Openstack-operators] [openstack-dev][openstack-operators][chef] OpenStack+Chef is part of the big tent

an questions or thoughts please don’t hesitate to reach out. [1]: https://review.openstack.org/#/c/175000/ <https://review.openstack.org/#/c/175000/> Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar___ OpenStack-operators mailing list Ope

Re: [Openstack-operators] CEPH - Ops Summit Working Session

ps://etherpad.openstack.org/p/YVR-ops-ceph> Thanks for this, I made a statement on it. I want to leverage the Ceph story for the OpenStack+Chef builds we have, and I’m at a loss on where to start. Could I steal some time of yall’s to help me figure out how I can make it happen? Th

Re: [Openstack-operators] chef

> On May 14, 2015, at 1:21 AM, aishwarya.adyanth...@accenture.com wrote: > > Hi J, > > I ran the command 'knife node list' and found the list to be empty while the > 'knife client list' command displays chef-validator and chef-webui. It seems > like when I was creating the node through knife

[Openstack-operators] [openstack-operators][chef] OpenStack-Chef Official Ops Meetup

> On May 12, 2015, at 3:00 PM, JJ Asghar wrote: > > I’d like to announce the OpenStack-Chef Ops Meetup in Vancouver. We have an > etherpad[1] going with topics people would like to discuss. I haven’t found a > room or space for us yet, but when I do I’ll comment back on this th

Re: [Openstack-operators] chef

Ashwarya, can you try knife node list and knife client list for me? You should see the the machine you’re attempting to create. I’m betting that there is a node like the error says, and you’ll need to do a knife node delete then run the bootstrap command again and it should work. -J _

[Openstack-operators] [openstack-operators][chef] OpenStack-Chef Ops Meetup

deal if you step up with some Chef Swag too ;). I hope to see you there and don’t hesitate to reach out if you have any relevant questions. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar [1]: https://etherpad.openstack.org/p/YVR-ops-chef <https://etherpad.openstack.org/p/YVR-ops-c

Re: [Openstack-operators] chef

nnel, and am almost always there. And to parriot what Abel is saying it looks like that issue is related to you not removing the node from your chef server, but we can talk more detail there. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators