[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

[Frank Kloeker]

Hi Chris,

thanks for summarize our session today in Vancouver. As I18n PTL and one 
of the Docs Core I put Petr in Cc. He is currently Docs PTL, but 
unfortunatelly not on-site.
I couldn't also not get the full history of the story and that's also 
not the idea to starting finger pointing. As usualy we moving forward 
and there are some interesting things to know what happened.
First of all: There are no "Docs-Team" anymore. If you look at [1] there 
are mostly part-time contributors like me or people are more involved in 
other projects and therefore busy. Because of that, the responsibility 
of documentation content are moved completely to the project teams. Each 
repo has a user guide, admin guide, deployment guide, and so on. The 
small Documentation Team provides only tooling and give advices how to 
write and publish a document. So it's up to you to re-use the old repo 
on [2] or setup a new one. I would recommend to use the best of both 
worlds. There are a very good toolset in place for testing and 
publishing documents. There are also various text editors for rst 
extensions available, like in vim, notepad++ or also online services. I 
understand the concerns and when people are sad because their patches 
are ignored for months. But it's alltime a question of responsibilty and 
how can spend people time.
I would be available for help. As I18n PTL I could imagine that a 
OpenStack Operations Guide is available in different languages and 
portable in different formats like in Sphinx. For us as translation team 
it's a good possibility to get feedback about the quality and to 
understand the requirements, also for other documents.

So let's move on.

kind regards

Frank

[1] https://review.openstack.org/#/admin/groups/30,members
[2] https://github.com/openstack/operations-guide

Am 2018-05-24 03:38, schrieb Chris Morgan:

Hello Everyone,

In the Ops Community documentation working session today in Vancouver,
we made some really good progress (etherpad here:
https://etherpad.openstack.org/p/YVR-Ops-Community-Docs but not all of
the good stuff is yet written down).

In short, we're going to course correct on maintaining the Operators
Guide, the HA Guide and Architecture Guide, not edit-in-place via the
wiki and instead try still maintaining them as code, but with a
different, new set of owners, possibly in a new Ops-focused repo.
There was a strong consensus that a) code workflow >> wiki workflow
and that b) openstack core docs tools are just fine.

There is a lot still to be decided on how where and when, but we do
have an offer of a rewrite of the HA Guide, as long as the changes
will be allowed to actually land, so we expect to actually start
showing some progress.

At the end of the session, people wanted to know how to follow along
as various people work out how to do this... and so for now that place
is this very email thread. The idea is if the code for those documents
goes to live in a different repo, or if new contributors turn up, or
if a new version we will announce/discuss it here until such time as
we have a better home for this initiative.

Cheers

Chris

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



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

[Openstack-operators] [I18n] [Docs] Forum session Vancouver

[Frank Kloeker]

Good morning,

just a quick note when packing the suitcase: We have a Docs/I18n Forum 
session on Monday 21th, 13:30, direct after lunch [1]. Take the chance 
to discuss topics about project onboarding with translation or 
documentation, usage of translated documents or tools. Or just come to 
say Hello :-)

Looking forward to see you there!

kind regards

Frank (PTL I18n)


[1] 
https://etherpad.openstack.org/p/docs-i18n-project-onboarding-vancouver


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

[Openstack-operators] [I18n] Office Hours, Thursday, 2018/04/26 13:00-14:00 UTC & 2018/05/03 07:00-08:00 UTC

[Frank Kloeker]

Hello,

the I18n team wants to change something in collaboration and 
communication with other teams and users. Instead of team meetings we 
offer around the Summit an open communication on Freenode IRC 
#openstack-i18n channel.  Feel free to add your topics on the wiki page 
on [1]. Or better join one of our Office Hours to discuss topis around 
I18n. We are especially interested on:


* Feedback about quality of translation in different languages
* New projects or documents with interests on translation
* New ideas like AI for I18n or new feature requests for Zanata, our 
translation platform


You can meet us in person together with Docs team on the Project 
Onboarding Session during the Vancouver Summit [2].


kind regards

Frank
PTL I18n

[1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting
[2] 
https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21627/docsi18n-project-onboarding



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