[Openstack-operators] Early Bird Pricing Ends Tomorrow - OpenStack Summit Berlin

[Kendall Waters]

Hi everyone,

Friendly reminder that the early bird ticket price deadline for the OpenStack 
Summit Berlin  is tomorrow, August 28 at 
11:59pm PT (August 29, 6:59 UTC). 

In Berlin, there will be sessions and workshops around open infrastructure use 
cases, including CI/CD, container infrastructure, edge computing, HPC / AI / 
GPUs, private & hybrid cloud, public cloud and NFV. In case you haven’t seen 
it, the agenda is now live 
 and includes 
sessions and workshops from Ocado Technology, Metronom, Oerlikon, and more! In 
addition, make sure to check out the Edge Hackathon hosted by Open Telekom 
Cloud 

 the weekend prior to the Summit.

Register NOW  before the 
price increases to $999 USD!

Interested in sponsoring the Summit? Find out more here 
 or email 
sum...@openstack.org.

Cheers,
Kendall

Kendall Waters
OpenStack Marketing & Events
kend...@openstack.org ___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Community Documentation - first anchor point

[Jeremy Stanley]

On 2018-08-27 11:06:42 -0400 (-0400), Doug Hellmann wrote:
[...]
> I do not see the flag that says the CLA is required in the configuration
> for the repository:
> 
> http://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/operations-guide.config

You can also tell by looking at the general project properties:

https://review.openstack.org/#/admin/projects/openstack/operations-guide

"Require a valid contributor agreement to upload" there is "INHERIT
(false)" which indicates it's not set.
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments

[Julia Kreger]

Greetings everyone!

We in Ironic land would like to go into the PTG with some additional
thoughts, requirements, and ideas as it relates to distributed and
geographically distributed deployments.

As you may or may not know, we did take a first step towards
supporting some of the architectures needed with conductor_groups this
past cycle, but we have two very distinct needs that have been
expressed with-in the community.

1) Need to federate and share baremetal resources between ironic
deployments. A specification[1] was proposed to try and begin to
capture what this would look like ironic wise. At a high level, this
would look like an ironic node that actually consumes and remotely
manages a node via another ironic deployment. Largely this would be a
stand-alone user/admin user deployment cases, where hardware inventory
insight is needed.

2) Need to securely manage remote sites with different security
postures, while not exposing control-plane components as an attack
surface. Some early discussion into this would involve changing
Conductor/IPA communication flow[2], or at least supporting a
different model, and some sort of light weight intermediate middle-man
service that helps facilitate the local site management.

With that in mind, we would like to schedule a call for sometime next
week where we can kind of talk through and discuss these thoughts and
needs in real time in advance of the PTG so we can be even better
prepared. We are attempting to identify a time with a doodle[3].
Please select a time and date, so we can schedule something for next
week.

Thanks,

-Julia

[1]: https://review.openstack.org/#/c/560152/
[2]: https://review.openstack.org/212206
[3]: https://doodle.com/poll/y355wt97heffvp3m

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [all] Berlin Hackathon: Hacking the Edge

[Frank Kloeker]

Hello,

For the weekend before the Berlin Summit we plan an additional
OpenStack community event: "Hacking the Edge" Hackathon.
The idea is to build together a community cloud based on
Edge technology.

We're looking for volunteers:

Developers
Try out the newest software version from your projects like Nova,
Cinder, and Neutron. What's the requirements for Edge and what
makes sense? Install different components on different devices and
connects all of them.

Operators
Operation of Edge Cloud is also a challenge. Changes from 'must be
online' to 'maybe online'. Which measuring methods are available for
monitoring? Where are my backups? Do we need an operation center
also in the Edge?

Architects
General Edge Cloud Architecture. How is the plan for connecting new
devices with different connectivity. Scalable application and
life cycle management.

Bring your own devices like laptop, Raspberry PI, WIFI routers, which
you would connect to the Edge Cloud.

We host the event location and provide infrastructure, maybe together
with a couple of 5G devices, because the venue has one of the first
5G antennas in Germany.

Everybody is welcome to join and have fun. We are only limited
on the event space.  More details are also in the event description.

Don't be afraid to ask me directly, via e-mail or IRC.

kind regards

Frank (eumel8)

Registration: https://openstack-hackathon-berlin.eventbrite.com/
Collected ideas/workpad:
https://etherpad.openstack.org/p/hacking_the_edge_hackathon_berlin

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Community Documentation - first anchor point

[Doug Hellmann]

Excerpts from Kunzmann, Gerald's message of 2018-08-27 12:37:28 +:
> Hi everyone,
> 
> I think this is a great step to pull together all Ops related discussions 
> into 
> one common repo and SIG.
> 
> I noticed that there was a proposal in the Vancouver discussion [1] to create 
> the repo without CLA. I am curious which way was the repo setup? Not 
> requiring 
> the CLA and also removing some steps from the "full openstack code workflow" 
> might indeed remove a potential barrier for contributions.
> 
> [1] https://etherpad.openstack.org/p/YVR-Ops-Community-Docs
> 
> Best regards,
> Gerald

I do not see the flag that says the CLA is required in the configuration
for the repository:

http://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/operations-guide.config

Doug

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Community Documentation - first anchor point

[Kunzmann, Gerald]

Hi everyone,

I think this is a great step to pull together all Ops related discussions into 
one common repo and SIG.

I noticed that there was a proposal in the Vancouver discussion [1] to create 
the repo without CLA. I am curious which way was the repo setup? Not requiring 
the CLA and also removing some steps from the "full openstack code workflow" 
might indeed remove a potential barrier for contributions.

[1] https://etherpad.openstack.org/p/YVR-Ops-Community-Docs

Best regards,
Gerald

-Original Message-
From: Sean McGinnis 
Sent: Dienstag, 21. August 2018 21:28
To: Jonathan Proulx 
Cc: OpenStack Operators 
Subject: Re: [Openstack-operators] Ops Community Documentation - first anchor 
point

On Tue, Aug 21, 2018 at 03:14:48PM -0400, Jonathan Proulx wrote:
> Hi All...
>
> I'm still a little confused by the state of this :)
>
> I know I made some promises then got distracted the looks like Sean
> stepped up and got things a bit further, but where is it now?  Do we
> have an active repo?
>
> It would be nice to have the repo in place before OPs meetup.
>
> -Jon
>

Hey Jon,

Pretty much everything is in place now. There is one outstanding patch to
officially add things under the SIG governance here:

https://review.openstack.org/#/c/591248/

That's a formality that needs to be done, but we do have the content being
published to the site:

https://docs.openstack.org/operations-guide/

And we have the repo set up and ready for updates to be proposed:

http://git.openstack.org/cgit/openstack/operations-guide

Our next step is to start encouraging contributions from the community. This
would be a great things to discuss at the PTG, and I now realize that I didn't
add this obvious thing to our ops PTG planning etherpad. I will add it there
and hopefully we can go over some of the content and get some more interest in
contributing to it.

Thanks!
Sean

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


smime.p7s
Description: S/MIME cryptographic signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators