Re: [openstack-dev] [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for Contributions - Deadline Approaching

2018-10-31 Thread Ildiko Vancsa


> On 2018. Oct 31., at 19:11, Mike Bayer  wrote:
> 
> On Wed, Oct 31, 2018 at 10:57 AM Bogdan Dobrelya  wrote:
>> 
>> (cross-posting openstack-dev)
>> 
>> Hello.
>> [tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data
>> consistency requirements and challenges" a position paper [0] (papers
>> submitting deadline is Nov 8).
>> 
>> The problem scope is synchronizing control plane and/or
>> deployments-specific data (not necessary limited to OpenStack) across
>> remote Edges and central Edge and management site(s). Including the same
>> aspects for overclouds and undercloud(s), in terms of TripleO; and other
>> deployment tools of your choice.
>> 
>> Another problem is to not go into different solutions for Edge
>> deployments management and control planes of edges. And for tenants as
>> well, if we think of tenants also doing Edge deployments based on Edge
>> Data Replication as a Service, say for Kubernetes/OpenShift on top of
>> OpenStack.
>> 
>> So the paper should name the outstanding problems, define data
>> consistency requirements and pose possible solutions for synchronization
>> and conflicts resolving. Having maximum autonomy cases supported for
>> isolated sites, with a capability to eventually catch up its distributed
>> state. Like global database [1], or something different perhaps (see
>> causal-real-time consistency model [2],[3]), or even using git. And
>> probably more than that?.. (looking for ideas)
> 
> 
> I can offer detail on whatever aspects of the "shared  / global
> database" idea.  The way we're doing it with Galera for now is all
> about something simple and modestly effective for the moment, but it
> doesn't have any of the hallmarks of a long-term, canonical solution,
> because Galera is not well suited towards being present on many
> (dozens) of endpoints. The concept that the StarlingX folks were
> talking about, that of independent databases that are synchronized
> using some kind of middleware is potentially more scalable, however I
> think the best approach would be API-level replication, that is, you
> have a bunch of Keystone services and there is a process that is
> regularly accessing the APIs of these keystone services and
> cross-publishing state amongst all of them.   Clearly the big
> challenge with that is how to resolve conflicts, I think the answer
> would lie in the fact that the data being replicated would be of
> limited scope and potentially consist of mostly or fully
> non-overlapping records.
> 
> That is, I think "global database" is a cheap way to get what would be
> more effective as asynchronous state synchronization between identity
> services.

Recently we’ve been also exploring federation with an IdP (Identity Provider) 
master: 
https://wiki.openstack.org/wiki/Keystone_edge_architectures#Identity_Provider_.28IdP.29_Master_with_shadow_users

One of the pros is that it removes the need for synchronization and potentially 
increases scalability.

Thanks,
Ildikó


> 
>> 
>> See also the "check" list in-line, which I think also meets the data
>> consistency topics well - it would be always nice to have some
>> theoretical foundations at hand, when repairing some
>> 1000-edges-spread-off and fully broken global database, by hand :)
>> 
>> PS. I must admit I have yet any experience with those IEEE et al
>> academic things and looking for someone who has it, to team and
>> co-author that positioning paper by. That's as a start, then we can
>> think of presenting it and expanding into work items for OpenStack Edge
>> WG and future development plans.
>> 
>> [0] http://conferences.computer.org/ICFC/2019/Paper_Submission.html
>> [1] https://review.openstack.org/600555
>> [2] https://jepsen.io/consistency
>> [3] http://www.cs.cornell.edu/lorenzo/papers/cac-tr.pdf
>> 
>> On 10/22/18 3:44 PM, Flavia Delicato wrote:
>>> =
>>> IEEE International Conference on Fog Computing (ICFC 2019)
>>> June 24-26, 2019
>>> Prague, Czech Republic
>>> http://conferences.computer.org/ICFC/2019/
>>> Co-located with the IEEE International Conference on Cloud Engineering
>>> (IC2E 2019)
>>> ==
>>> 
>>> Important Dates
>>> ---
>>> Paper registration and abstract: Nov 1st, 2018
>>> Full paper submission due: Nov 8th, 2018
>>> Notification of paper acceptance: Jan. 20th, 2019
>>> Workshop and tutorial proposals due: Nov 11, 2018
>>> Notification of proposal acceptance: Nov 18, 2018
>>> 
>>> Call for Contributions
>>> --
>>> Fog computing is the extension of cloud computing into its edge and
>>> the physical world to meet the data volume and decision velocity
>>> requirements in many emerging applications, such as augmented and
>>> virtual realities (AR/VR), cyber-physical systems (CPS), intelligent
>>> and autonomous systems, and mission-critical systems. The boundary
>>> 

Re: [openstack-dev] [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for Contributions - Deadline Approaching

2018-10-31 Thread Ildiko Vancsa
Hi,

Thank you for sharing your proposal.

I think this is a very interesting topic with a list of possible solutions some 
of which this group is also discussing. It would also be great to learn more 
about the IEEE activities and have experience about the process in this group 
on the way forward.

I personally do not have experience with IEEE conferences, but I’m happy to 
help with the paper if I can.

Thanks,
Ildikó


> On 2018. Oct 31., at 17:53, Bogdan Dobrelya  wrote:
> 
> I forgot to mention the submission registration and abstract has to be 
> submitted today. I've created it as #1570506394, and the paper itself can be 
> uploaded until the Nov 8 (or Nov 9 perhaps as the registration system shows 
> to me). I'm not sure that paper number is searchable publicly, so here is the 
> paper name and abstract for your kind review please:
> 
> name: "Edge clouds control plane and management data consistency challenges"
> abstract: "Fog computing is emerging Cloud of (Edge) Clouds technology. Its 
> control plane and deployments data synchronization is a major challenge. 
> Autonomy requirements expect even the most distant edge sites always 
> manageable, available for monitoring and alerting, scaling up/down, upgrading 
> and applying security fixes. Whenever temporary disconnected sites are 
> managed locally or centrally, some changes and data need to be eventually 
> synchronized back to the central site(s) with having its merge-conflicts 
> resolved for the central data hub(s). While some data needs to be pushed from 
> the central site(s) to the Edge, which might require resolving data 
> collisions at the remote sites as well. In this paper, we position the 
> outstanding data synchronization problems for OpenStack cloud platform 
> becoming a solution number one for fog computing. We outline the data 
> consistency requirements and design approaches to meet the AA (Always 
> Available) autonomy expectations. Finally, the paper brings the vision of 
> unified tooling, which solves the data synchronization problems the same way 
> for infrastructure owners, IaaS cloud operators and tenants running workloads 
> for PaaS like OpenShift or Kubernetes deployed on top of OpenStack. The 
> secondary goal of this work is to help cloud architects and developers to 
> federate stateful cloud components over reliable distributed data backends 
> and having its failure modes known."
> Thank you  for your time, if still reading this.
> 
> On 10/31/18 3:57 PM, Bogdan Dobrelya wrote:
>> (cross-posting openstack-dev)
>> Hello.
>> [tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data 
>> consistency requirements and challenges" a position paper [0] (papers 
>> submitting deadline is Nov 8).
>> The problem scope is synchronizing control plane and/or deployments-specific 
>> data (not necessary limited to OpenStack) across remote Edges and central 
>> Edge and management site(s). Including the same aspects for overclouds and 
>> undercloud(s), in terms of TripleO; and other deployment tools of your 
>> choice.
>> Another problem is to not go into different solutions for Edge deployments 
>> management and control planes of edges. And for tenants as well, if we think 
>> of tenants also doing Edge deployments based on Edge Data Replication as a 
>> Service, say for Kubernetes/OpenShift on top of OpenStack.
>> So the paper should name the outstanding problems, define data consistency 
>> requirements and pose possible solutions for synchronization and conflicts 
>> resolving. Having maximum autonomy cases supported for isolated sites, with 
>> a capability to eventually catch up its distributed state. Like global 
>> database [1], or something different perhaps (see causal-real-time 
>> consistency model [2],[3]), or even using git. And probably more than 
>> that?.. (looking for ideas)
>> See also the "check" list in-line, which I think also meets the data 
>> consistency topics well - it would be always nice to have some theoretical 
>> foundations at hand, when repairing some 1000-edges-spread-off and fully 
>> broken global database, by hand :)
>> PS. I must admit I have yet any experience with those IEEE et al academic 
>> things and looking for someone who has it, to team and co-author that 
>> positioning paper by. That's as a start, then we can think of presenting it 
>> and expanding into work items for OpenStack Edge WG and future development 
>> plans.
>> [0] http://conferences.computer.org/ICFC/2019/Paper_Submission.html
>> [1] https://review.openstack.org/600555
>> [2] https://jepsen.io/consistency
>> [3] http://www.cs.cornell.edu/lorenzo/papers/cac-tr.pdf
>> On 10/22/18 3:44 PM, Flavia Delicato wrote:
>>> =
>>>  
>>> IEEE International Conference on Fog Computing (ICFC 2019)
>>> June 24-26, 2019
>>> Prague, Czech Republic
>>> http://conferences.computer.org/ICFC/2019/
>>> Co-located with the IEEE 

[openstack-dev] Announcing the First Release of StarlingX, an open source edge computing platform

2018-10-24 Thread Ildiko Vancsa
Hi,

You may have heard, StarlingX[1] is a new independent, top-level, open source 
pilot project that's supported by the OpenStack Foundation. StarlingX joins 
other pilot projects hosted at OpenStack Foundation[2], including Airship, Kata 
Containers and Zuul.

Today the first release of StarlingX is here!

We invite you to participate in getting the word out that the release is ready 
and that we’re eager to welcome more contributors to this project.

Learn more about it:
• Read more about the project at starlingx.io
• Listen to a recording of the onboarding webinar[3]
• On-boarding slide deck[4]
• Overview document[5]

Some things you can share:
• A blog on starlingx.io[6]
• Social sharing: Announcements on Twitter[7]

Want to get involved in the community?
• Mailing Lists[8] 
• Weekly Calls[9]
• Freenode IRC: #starlingx channel[10]

Ready to dive into the code?
• You can get download the first release at git.starlingx.io 
• StarlingX Install Guide[11] 
• StarlingX Developer Guide[12]

If you’re at the Berlin Summit November 13-15[13]:
Tuesday 11/13
• StarlingX – Project update – 6 months in the life of a new Open Source 
project with Brent Rowsell & Dean Troyer
• StarlingX CI, from zero to Zuul with Hazzim Anaya & Elio Martinez

Wednesday 11/14 
• Keynote spotlight on the main stage with Ian Jolliffe & Dean Troyer
• MVP (Minimum Viable Product) architecture for edge - Forum session
• "Ask Me Anything" about StarlingX - Forum session
• StarlingX Enhancements for Edge Networking presentation with Kailun Qin, 
Ruijing Guo & Dan Chen
• Project Onboarding session with Greg Waines
• Integrating IOT Device Management with the Edge Cloud - Forum session

Thursday 11/15
• Containerized Applications' Requirements on Kubernetes Cluster at the Edge - 
Forum session

Check out the materials to learn about the project, try out the software and 
join the community! We hope to see many of you in Berlin!

Ildikó

[1] https://www.starlingx.io/ 
[2] https://www.openstack.org/foundation/
[3] https://www.youtube.com/watch?v=G9uwGnKD6tM=232s 
[4] https://www.starlingx.io/collateral/StarlingX-Onboarding-Deck-Web.pdf 
[5] https://www.starlingx.io/collateral/StarlingX_OnePager_Web-102318pdf/
[6] https://www.starlingx.io/blog/starlingx-initial-release.html
[7] https://twitter.com/starlingx
[8] http://lists.starlingx.io/cgi-bin/mailman/listinfo
[9] https://wiki.openstack.org/wiki/Starlingx/Meetings
[10] https://freenode.net/
[11] https://docs.starlingx.io/installation_guide/index.html
[12] https://docs.starlingx.io/developer_guide/index.html
[13] https://www.openstack.org/summit/berlin-2018
__
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] [os-upstream-institute] Cancelling the bi-weekly meetings

2018-10-06 Thread Ildiko Vancsa
Hi Training Team,

As a follow up from our last call we agreed to cancel the regular IRC meetings 
as we do not have that many regular topics to discuss.

We will keep scheduling ad-hoc calls to prepare for the trainings before the 
Summits and utilize the mailing list and the IRC channel for communication.

Please raise your concern __before October 12__ in case you don’t agree with 
this decision. If I don’t receive any concerns or preference on keeping the 
meeting till that date I will go ahead and remove it form the community 
calendar.

Please let me know if you have questions.

Thanks and Best Regards,
Ildikó



__
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] [os-upstream-institute] Sync calls with the mentors for Berlin

2018-10-06 Thread Ildiko Vancsa
Hi,

We are planning two calls to prepare for the Berlin Summit. One is some time 
between Oct 15 and 23 and the other is the week of November 5 which is the week 
before the Summit.

The purpose of the first call is to go through the training material and 
prepare for the training. We will check the slides and the exercises and check 
whether we have any missing items or things to correct in the Contributor guide.

The second call will be for checking back on action items and discuss any last 
minute administrativa.

I created a Doodle poll to find the best times within the two aforementioned 
periods: https://doodle.com/poll/3ctqzkikn7prnpgg

Please mark __all the slots__ that can work for you, even if it is not the most 
convenient time of the day as we will only have two of these calls.

If you plan to join the crew for Berlin and you haven’t signed up yet on the 
wiki please do it here: 
https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó



__
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] [os-upstream-institute] Find a slot for a meeting to discuss - ACTION NEEDED

2018-09-29 Thread Ildiko Vancsa
Hi Training Team,

Based on the votes on the Doodle poll below we will have our ad-hoc meeting 
__next Friday (October 5) 1600 UTC__.

Hangouts link for the call: 
https://hangouts.google.com/call/BKnvu7e72uB_Z-QDHDF2AAEI

If you’re available for the Berlin training as mentor and haven’t signed up on 
the wiki yet please do so: 
https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions#Berlin_Crew

Please let me know if you have any questions.

Thanks,
Ildikó



> On 2018. Sep 23., at 14:29, Ildiko Vancsa  wrote:
> 
> Hi Training Team,
> 
> With the new workshop style training format that is utilizing the Contributor 
> Guide we have less work with the training material side and we have less 
> items to discuss in the form of regular meetings.
> 
> However, we have a few items to go through before the upcoming training in 
> Berlin to make sure we are fully prepared. We also have Florian from City 
> Network working on the online version of the training that he would like to 
> discuss with the team.
> 
> As the current meeting slot is very inconvenient in Europe and Asia as well I 
> put together a Doodle poll to try to find a better slot if we can. As we have 
> people all around the globe all the slots are inconvenient to a subset of the 
> team, but if we can agree on one for one meeting it would be great.
> 
> Please vote on the poll as soon as possible: 
> https://doodle.com/poll/yrp9anbb7weaun4h
> 
> When we have the full list of mentors for the Berlin training I will send out 
> a separate poll for one or two prep calls. If you’re available for the 
> training and not signed up on the wiki yet please sign up: 
> https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions#Berlin_Crew
> 
> Please let me know if you have any questions.
> 
> Thanks and Best Regards,
> Ildikó
> 
> 


__
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] [cinder][glance][ironic][keystone][neutron][nova][edge] PTG summary on edge discussions

2018-09-25 Thread Ildiko Vancsa
Hi,

Hereby I would like to give you a short summary on the discussions that 
happened at the PTG in the area of edge.

The Edge Computing Group sessions took place on Tuesday where our main activity 
was to draw an overall architecture diagram to capture the basic setup and 
requirements of edge towards a set of OpenStack services. Our main and initial 
focus was around Keystone and Glance, but discussion with other project teams 
such as Nova, Ironic and Cinder also happened later during the week.

The edge architecture diagrams we drew are part of a so called Minimum Viable 
Product (MVP) which refers to the minimalist nature of the setup where we 
didn’t try to cover all aspects but rather define a minimum set of services and 
requirements to get to a functional system. This architecture will evolve 
further as we collect more use cases and requirements.

To describe edge use cases on a higher level with Mobile Edge as a use case in 
the background we identified three main building blocks:

* Main or Regional Datacenter (DC)
* Edge Sites
* Far Edge Sites or Cloudlets

We examined the architecture diagram with the following user stories in mind:

* As a deployer of OpenStack I want to minimize the number of control planes I 
need to manage across a large geographical region.
* As a user of OpenStack I expect instance autoscale continues to function in 
an edge site if connectivity is lost to the main datacenter.
* As a deployer of OpenStack I want disk images to be pulled to a cluster on 
demand, without needing to sync every disk image everywhere.
* As a user of OpenStack I want to manage all of my instances in a region (from 
regional DC to far edge cloudlets) via a single API endpoint. 

We concluded to talk about service requirements in two major categories:

1. The Edge sites are fully operational in case of a connection loss between 
the Regional DC and the Edge site which requires control plane services running 
on the Edge site
2. Having full control on the Edge site is not critical in case a connection 
loss between the Regional DC and an Edge site which can be satisfied by having 
the control plane services running only in the Regional DC

In the first case the orchestration of the services becomes harder and is not 
necessarily solved yet, while in the second case you have centralized control 
but losing functionality on the Edge sites in the event of a connection loss.

We did not discuss things such as HA at the PTG and we did not go into details 
on networking during the architectural discussion either.

We agreed to prefer federation for Keystone and came up with two work items to 
cover missing functionality:

* Keystone to trust a token from an ID Provider master and when the auth method 
is called, perform an idempotent creation of the user, project and role 
assignments according to the assertions made in the token
* Keystone should support the creation of users and projects with predictable 
UUIDs (eg.: hash of the name of the users and projects). This greatly 
simplifies Image federation and telemetry gathering

For Glance we explored image caching and spent some time discussing the option 
to also cache metadata so a user can boot new instances at the edge in case of 
a network connection loss which would result in being disconnected from the 
registry:

* I as a user of Glance, want to upload an image in the main datacenter and 
boot that image in an edge datacenter. Fetch the image to the edge datacenter 
with its metadata

We are still in the progress of documenting the discussions and draw the 
architecture diagrams and flows for Keystone and Glance.


In addition to the above we went through Dublin PTG wiki 
(https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG) 
capturing requirements:

* we agreed to consider the list of requirements on the wiki finalized for now
* agreed to move there the additional requirements listed on the Use Cases 
(https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases) wiki page

For the details on the discussions with related OpenStack projects you can 
check the following etherpads for notes:

* Cinder: https://etherpad.openstack.org/p/cinder-ptg-planning-denver-9-2018
* Glance: https://etherpad.openstack.org/p/glance-stein-edge-architecture
* Ironic: https://etherpad.openstack.org/p/ironic-stein-ptg-edge
* Keystone: https://etherpad.openstack.org/p/keystone-stein-edge-architecture
* Neutron: https://etherpad.openstack.org/p/neutron-stein-ptg
* Nova: https://etherpad.openstack.org/p/nova-ptg-stein

Notes from the StarlingX sessions: 
https://etherpad.openstack.org/p/stx-PTG-agenda


We are still working on the MVP architecture to clean it up and discuss 
comments and questions before moving it to a wiki page. Please let me know if 
you would like to get access to the document and I will share it with you.

Please let me know if you have any questions or comments to the above captured 
items.

Thanks and Best Regards,

[openstack-dev] [os-upstream-institute] Find a slot for a meeting to discuss - ACTION NEEDED

2018-09-23 Thread Ildiko Vancsa
Hi Training Team,

With the new workshop style training format that is utilizing the Contributor 
Guide we have less work with the training material side and we have less items 
to discuss in the form of regular meetings.

However, we have a few items to go through before the upcoming training in 
Berlin to make sure we are fully prepared. We also have Florian from City 
Network working on the online version of the training that he would like to 
discuss with the team.

As the current meeting slot is very inconvenient in Europe and Asia as well I 
put together a Doodle poll to try to find a better slot if we can. As we have 
people all around the globe all the slots are inconvenient to a subset of the 
team, but if we can agree on one for one meeting it would be great.

Please vote on the poll as soon as possible: 
https://doodle.com/poll/yrp9anbb7weaun4h

When we have the full list of mentors for the Berlin training I will send out a 
separate poll for one or two prep calls. If you’re available for the training 
and not signed up on the wiki yet please sign up: 
https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions#Berlin_Crew

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó



__
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] [os-upstream-institute][all] Upstream Institute training call for mentors!!

2018-09-20 Thread Ildiko Vancsa
Hi,

We have two Upstream Institute trainings [1] upcoming and we are looking for 
mentors to join us and help new contributors to start their journey in 
OpenStack.

We have a training in Stockholm on October 9 and one in Berlin right before the 
Summit on November 11-12. If you are available for each or both of these 
occasions and interested to join our crew please sign up on our wiki page [2].

If you have any questions please reply to this thread or reach out to the team 
on the #openstack-upstream-institute IRC channel.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)

[1] https://docs.openstack.org/upstream-training/#upcoming-trainings
[2] https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions
__
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] [os-upstream-institute] Team lunch at the PTG next week - ACTION NEEDED

2018-09-12 Thread Ildiko Vancsa
Hi,

Wednesday is already here so let’s meet for lunch today!

We will have a table reserved for us in the lunch room (Ballroom D), let’s meet 
there so we can catch up a little before the Berlin Summit. :)

Thanks,
Ildikó


> On 2018. Sep 9., at 15:20, Ghanshyam Mann  wrote:
> 
> I am in for Wed lunch meeting. 
> 
> -gmann
> 
>  On Sat, 08 Sep 2018 07:30:53 +0900 Ildiko Vancsa 
>  wrote  
>> Hi Training Team,
>> 
>> As a couple of us will be at the PTG next week it would be great to get 
>> together one of the days maybe for lunch.
>> 
>> Wednesday would work the best for Kendall and me, but we can look into other 
>> days as well if it would not work for the majority of people around.
>> 
>> So my questions would be:
>> 
>> * Are you interested in getting together one of the lunch slots during next 
>> week?
>> 
>> * Would Wednesday work for you or do you have another preference?
>> 
>> Please drop a response to this thread and we will figure it out by Monday or 
>> early next week based on the responses.
>> 
>> Thanks,
>> Ildikó
>> (IRC: ildikov)
>> 
>> 
>> 
>> __
>> 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-dev] [os-upstream-institute] Team lunch at the PTG next week - ACTION NEEDED

2018-09-07 Thread Ildiko Vancsa
Hi Training Team,

As a couple of us will be at the PTG next week it would be great to get 
together one of the days maybe for lunch.

Wednesday would work the best for Kendall and me, but we can look into other 
days as well if it would not work for the majority of people around.

So my questions would be:

* Are you interested in getting together one of the lunch slots during next 
week?

* Would Wednesday work for you or do you have another preference?

Please drop a response to this thread and we will figure it out by Monday or 
early next week based on the responses.

Thanks,
Ildikó
(IRC: ildikov)



__
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] [Openstack-operators] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments

2018-09-05 Thread Ildiko Vancsa
Hi,

I mentioned a non-official project on the call we had this week for IoT (bare 
metal) management, called IoTronic. It is developed in connection to a Smart 
Cities use case, the name of the project is Stack4Things under the #SmartME 
umbrella project, mostly revolving around Single-Board Computers (Raspberrys, 
Arduinos, etc) as full-blown (far) edge nodes.

IoTronic at this point is interoperating/integrated with 
Horizon/Keystone/Neutron.

You can find information on the following link about the umbrella projects and 
IoTronic:

Latest talk about Stack4Things/IoTronic, at the (Vancouver) Summit (includes 
link to video):
https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21201/an-edge-computing-case-study-for-monasca-smart-city-ai-powered-surveillance-and-monitoring

Official Stack4Things page (updates in progress, with high-level documentation, 
papers, etc)
http://stack4things.unime.it/

#SmartME Smart City (Messina) portal
http://smartme.unime.it/

#SmartME Open Data portal
http://smartme-data.unime.it 

OpenStack Infra-hosted repos for IoTronic
http://git.openstack.org/cgit/openstack/iotronic
http://git.openstack.org/cgit/openstack/iotronic-lightning-rod 
http://git.openstack.org/cgit/openstack/iotronic-ui
http://git.openstack.org/cgit/openstack/python-iotronicclient

Thanks,
Ildikó


> On 2018. Aug 31., at 6:50, Emilien Macchi  wrote:
> 
> On Fri, Aug 31, 2018 at 4:42 AM Dmitry Tantsur  wrote:
> This is about a call a week before the PTG, not the PTG itself. You're still 
> very welcome to join!
> 
> It's good too! Our TripleO IRC meeting is at 14 UTC.
> 
> 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] [glance][keystone][nova][ironic][tripleo][edge][airship] Edge related joint sessions at the PTG next week

2018-09-05 Thread Ildiko Vancsa
Hi,

The PTG is approaching quickly and as we are planning a couple of joint 
sessions on edge computing with a couple of OpenStack project teams I would 
like to give a quick summary of the plans.

We have the Edge Computing Group meeting all day Tuesday in Ballroom A[1] from 
9am MDT. The group is planning a use cases and requirements discussion in the 
morning and collaborative sessions with Glance, Keystone, Nova, Airship, 
TripleO and StarlingX throughout the day. Furthermore people from the group 
will participate in the relevant session on the Ironic agenda on Thursday.

For the full agenda and session topics please see the following etherpad: 
https://etherpad.openstack.org/p/EdgeComputingGroupPTG4

The StarlingX project is meeting all day Wednesday in Winter Park[1] starting 
at 9am MDT. Their topics include discussions on initial governance and release 
planning and further technical topics concerning architecture, build and 
deployment. The StarlingX team will participate in the cross-project sessions 
on Tuesday listed on the Edge Group etherpad for cross-project discussions.

For the full agenda of StarlingX sessions please see the following etherpad: 
https://etherpad.openstack.org/p/stx-PTG-agenda

Both groups are planning to provide remote participation option for their 
sessions, the information will be provided on the etherpads above before the 
sessions start.

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)

[1] https://web14.openstack.org/assets/ptg/Denver-map.pdf



__
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] [os-upstream-institute] Restarting meetings on August 20

2018-08-12 Thread Ildiko Vancsa
Hi,

As the Summer vacation season is getting to its end and we also need to start 
to prepare for the training just before the Berlin Summit we plan to resurrect 
the OUI meetings on every second Monday at 2000 UTC starting on August 20.

We will post the agenda on the regular etherpad: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings


Further useful links:

You can see the current state of the website: 
https://docs.openstack.org/upstream-training/index.html
The current training content can be found here: 
https://docs.openstack.org/upstream-training/upstream-training-content.html
To check the latest stage of the Contributor Guide: 
https://docs.openstack.org/contributors/index.html

Open training-guide reviews: 
https://review.openstack.org/#/q/project:openstack/training-guides+status:open
Open Contributor Guide reviews: 
https://review.openstack.org/#/q/project:openstack/contributor-guide+status:open

Contributor Guide StoryBoard open Stories/Tasks: 
https://storyboard.openstack.org/#!/project/913


Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)



__
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] [keystone] Cross-project discussions about Keystone for Edge at the PTG

2018-08-12 Thread Ildiko Vancsa
Hi,

The Keystone, Edge Computing Group and StarlingX teams are planning to have 
follow up discussions about using Keystone in edge scenarios including 
discussing requirements, architecture options and currently ongoing activities.

If you are interested in participating you can find further information here: 
http://lists.openstack.org/pipermail/edge-computing/2018-August/000394.html

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó



__
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] [keystone] Federation testing

2018-07-11 Thread Ildiko Vancsa
Hi,

Within the Edge Computing Group we have a few people interested in Keystone 
federation testing starting with general federation and moving to edge specific 
test cases onwards.

In case you are interested in this activity, we are organizing a call for next 
Thursday to talk about basic testing in OpenStack including identifying tasks 
and volunteers to complete them. We would like to use the time to clarify 
questions about Keystone federation capabilities if there’s any.

We are also collaborating with the OPNFV Edge Cloud project for advanced test 
scenarios which we will also discuss on the call.

The call details are here: 
https://wiki.openstack.org/wiki/Edge_Computing_Group#Federation_Testing_Call

Please check out the materials on this etherpad prior to the call if you plan 
to join: https://etherpad.openstack.org/p/ECG_Keystone_Testing

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó



__
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] [os-upstream-institute] Meeting reminder

2018-05-07 Thread Ildiko Vancsa
Hi Training Team,

It’s a friendly reminder that our next meeting is in an hour, 2000 UTC, on 
#openstack-meeting-3.

Agenda is here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you in a bit!

Thanks,
Ildikó
(IRC: ildikov)



__
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] [os-upstream-institute] Meeting reminder

2018-04-30 Thread Ildiko Vancsa
Hi,

Don’t forget that we switched to the US - Europe slot only till the training in 
Vancouver.

See you on #openstack-meeting-3 at 2000 UTC!

Thanks,
Ildikó (IRC: ildikov)



__
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] [os-upstream-institute] Prep call for Vancouver today - Minutes

2018-04-24 Thread Ildiko Vancsa
Hi All,

I would like to thank all of you who were able to join to our planning call 
yesterday for the Vancouver training.

For meeting minutes please visit the following etherpad: 
https://etherpad.openstack.org/p/OUI-AIO-guide-planning

We also recorded the call, so those of you who couldn’t dial in can listen to 
the whole discussion here: 
https://zoom.us/recording/share/7ysh3YPRjhCh8cS7iJcT9EttcJ7cC3IBIpgshOCD9CuwIumekTziMw

As we have only a couple of weeks and a lot of tasks to complete left, please 
look in to the corresponding StoryBoard project and pick an item to complete: 
https://storyboard.openstack.org/#!/project/913

We are planning one more sync call the week of the training. We are aiming for 
May 14 at 2200 UTC, but it’s still subject to change so stay tuned for further 
info.

Also please note that __until the Vancouver training we will keep all our 
meetings on Mondays at 2000 UTC__.

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)


> On 2018. Apr 23., at 22:08, Ildiko Vancsa <ildiko.van...@gmail.com> wrote:
> 
> Hi Training Team,
> 
> It is a friendly reminder that we will have a conference call on Zoom today 
> at 2200 UTC as opposed to the weekly meeting to better sync up before the 
> training in Vancouver.
> 
> You can find the call details here: 
> https://etherpad.openstack.org/p/openstack-upstream-institute-meetings
> 
> Please let me know if you have any questions.
> 
> Thanks,
> Ildikó
> (IRC: ildikov)
> 
> 


__
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] [os-upstream-institute] Prep call for Vancouver today

2018-04-23 Thread Ildiko Vancsa
Hi Training Team,

It is a friendly reminder that we will have a conference call on Zoom today at 
2200 UTC as opposed to the weekly meeting to better sync up before the training 
in Vancouver.

You can find the call details here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

Please let me know if you have any questions.

Thanks,
Ildikó
(IRC: ildikov)



__
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] [os-upstream-institute] Call before the Vancouver training - ACTION NEEDED

2018-04-03 Thread Ildiko Vancsa
Hi Training Team,

Our next training in Vancouver[1] is quickly approaching and we still have a 
lot of work to do.

In order to sync up I created a Doodle poll[2] with hours that are somewhat 
inconvenient, but can work around the globe. Please respond to the poll so we 
can setup a call to check on where we are and do last minute changes if needed.

In the meantime we are moving content over from the training-guides slides to 
the Contributor Guide[3], please pick a task and help out!

We also need to work on the exercises to keep the training interactive and 
hands on. If you have ideas please respond to this thread, jump on our IRC 
channel (#openstack-upstream-institute) or propose a patch to the training 
guides repository. :)

Let me know if you have any questions.

Thanks,
Ildikó (IRC: ildikov)

[1] 
https://www.openstack.org/summit/vancouver-2018/summit-schedule/global-search?t=Upstream+Institute
[2] https://doodle.com/poll/i894hhd7bfukmm7p
[3] https://storyboard.openstack.org/#!/project/913



__
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] [os-upstream-institute][ptg] Working sessions at the PTG

2018-02-14 Thread Ildiko Vancsa
Hi,

As discussed earlier we would like to leverage the opportunity to face to face 
working sessions at the PTG with the training team and anyone who’s interested 
to join/help out.

We have one dedicated time slot to meet and summarize our activities during the 
week and list of action points which is __Thursday 4pm-6pm__ local time. I will 
announce the room for the discussion in a follow up email.

To extend the time to work together in smaller groups we came up with the idea 
of a fixed work space, rather than a list of fixed time slots. The idea is to 
have a table dedicated to our team in the venue where anyone who’s not occupied 
can go and meet up with others to work on tasks we need to finish before the 
next training in Vancouver. Based on an earlier check the expectation is to 
have people available from Tuesday afternoon.

You can use the IRC channel and the PTG bot to inform others about your 
availability to further encourage team work.

The topics[1] for these working sessions are mainly focused on restructuring 
the training flow and improve the exercises.

For discussions on the Contributor Guide content please check the Docs 
sessions[2], we will cover all related topics there including moving the 
lectures over from the training guides repository. With that said we will also 
need to look into the translation aspects of the planned changes to keep 
supporting the broad community who relies on our materials.

Last but not least please also try to attend the First Contact SIG 
discussions[3] as they are relevant to the training activities as well and can 
affect how we structure and execute our courses in the future.

I will update you with details as we are getting closer to the PTG.

Please let me know if you have any questions or comments.

Thanks and Best Regards,
Ildikó

[1] https://etherpad.openstack.org/p/OUI-Rocky-PTG
[2] https://etherpad.openstack.org/p/docs-i18n-ptg-rocky
[3] https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG




__
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] [os-upstream-institute][ptg] Schedule Upstream Institute working sessions for the PTG

2018-01-30 Thread Ildiko Vancsa
Hi Training Team,

Good news, we are planning to have working sessions at the PTG! :)

The challenging part is that all of us are involved in several activities which 
makes it difficult to schedule these. We are looking into co-locating some 
parts of the discussions with related sessions, like First Contact SIG and 
Contributor Portal discussions.

On top of these we need to get rolling on re-designing the training including 
the flow and the exercises, which requires its own set of work sessions. In 
order to get most of the team in the same room I created a Doodle poll[1] 
capturing mornings and afternoons to find the best options. Please mark ALL the 
time intervals that might work for you!

We will also try to make it as a virtual working session with remote 
participation so please vote even if you cannot make it to the PTG in person.

Please let me know if you have any questions.

Thanks,
Ildikó
(IRC: ildikov)


[1] https://doodle.com/poll/y4cmhe2ur2vqkhae
__
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] [os-upstream-institute] Meeting reminder

2018-01-29 Thread Ildiko Vancsa
Hi Training Team,

Friendly reminder that we have our next meeting in an hour (2000 UTC) on 
#openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó
(IRC: ildikov)
__
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] [os-upstream-institute] Meeting on the 12th is cancelled

2017-12-11 Thread Ildiko Vancsa
Hi All,

I’m out of town in a time zone that doesn’t compatible with the meeting this 
Tuesday (Dec 12).

Our highest priority item right now is to move forward with migrating content 
form the training guides repository over to the Contributor Portal. Please look 
into the tasks on StoryBoard for the migration and pick some to complete and/or 
add new items: https://storyboard.openstack.org/#!/project/913

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)





__
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] [nova][cinder] Nova is now using the Cinder volume attachments API - multiattach comes next

2017-12-10 Thread Ildiko Vancsa
Thanks Matt for all the help so far and also for taking the time to write up 
this summary! I would like to join in saying thanks to the handful of people 
listed below who formed an amazing cross-project team during the past two years.

I strongly believe that by hunting for multi-attach support we stepped on the 
right track in terms of the interactions between the API’s of Cinder and Nova 
and better readability and maintainability of the code base in both projects on 
the long run with the changes we’ve made so far.

I hope we can grow our team onwards as testing will become even more crucial as 
we move forward with the remaining implementation work to reach the minimum 
functionality for multi-attach.

Thank you All once more for the hard work! And see you on the weekly meeting 
next Thursday. :)

Thanks,
Ildikó
(IRC: ildikov)


> On 2017. Dec 9., at 13:15, Matt Riedemann <mriede...@gmail.com> wrote:
> 
> I just wanted to take a minute to recognize that the patch [1] to make Nova 
> use the new-style Cinder volume attach flow has merged.
> 
> As one can tell from the patch set count alone, this has been in the works 
> for a long time now.
> 
> We were talking about volume multi-attach support back in Mitaka at the 
> midcycle in Bristol. The early talks / patches would have piled more 
> technical debt onto Nova and further baked in Nova's need to manage volume 
> state, which is something we wanted to avoid, so at the Newton summit in 
> Austin we changed course and decided to prioritize working on a new data 
> model and API in Cinder, which eventually came out as the 3.27 volume 
> attachments API in Ocata.
> 
> There was then serious work on both sides in Pike to start using the new 3.27 
> API and we found out we needed some more changes to Cinder, which became the 
> 3.44 Cinder API in Queens. Now Nova has merged the change at the end of a 
> very long series of changes to enable the new flow once 3.44 is available to 
> Nova and computes are all upgraded to understand the new flow. One can 
> appreciate the complexity here if you read through the Nova spec for the new 
> attach flow [2].
> 
> I was really happy to see [1] merge this week because I knew we needed to get 
> that in by the queens-2 milestone if we were going to have a shot at (1) 
> flushing out stability issues before Queens RC1 and (2) a good chance to get 
> multi-attach support into Nova in Queens.
> 
> We have a plan for multi-attach support [3] which I think is doable before 
> feature freeze. The Cinder 3.48 API is now available too which Nova needs to 
> correctly detach a multi-attach volume.
> 
> I want to thank everyone that's helped push this along for their dedication 
> and patience, especially John Griffith, Ildiko Vancsa, Steve Noyes and John 
> Garbutt. And thanks to Sean McGinnis, Jay Bryant, Walter Boring and Balazs 
> Gibizer for review support.
> 
> We've had weekly meetings between the Nova and Cinder teams for at least two 
> years now and I can finally see the end so let's keep up the momentum.
> 
> [1] https://review.openstack.org/#/c/330285/
> [2] 
> https://specs.openstack.org/openstack/nova-specs/specs/queens/approved/cinder-new-attach-apis.html
> [3] 
> https://specs.openstack.org/openstack/nova-specs/specs/queens/approved/cinder-volume-multi-attach.html
> 
> -- 
> 
> Thanks,
> 
> Matt
> 
> __
> 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] [os-upstream-institute] Meeting reminder

2017-12-04 Thread Ildiko Vancsa
Hi Training Team,

Friendly reminder that we have our next meeting in less than an hour (2000 UTC) 
on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó
(IRC: ildikov)
__
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] [os-upstream-institute] Meeting reminder

2017-11-20 Thread Ildiko Vancsa
Hi All,

Friendly reminder that our next meeting is in 10 minutes on 
#openstack-meeting-3.

Meeting agenda etherpad: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

Thanks and Best Regards,
Ildikó



__
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] [os-upstream-institute] Today's meeting is cancelled

2017-10-31 Thread Ildiko Vancsa
Hi All,

Today’s meeting is cancelled due to travels this week.

Please keep an eye on the open reviews and do any last minute fixes on the 
material that you can find.

Safe travels to those of you who’re coming to Sydney!

Best Regards,
Ildikó
(IRC: ildikov)



__
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] [os-upstream-institute] Meeting reminder

2017-10-23 Thread Ildiko Vancsa
HI Training Team,

Our next meeting is in less than an hour at 2000 UTC on #openstack-meeting-3.

The meeting agenda is here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you on IRC in a bit! :)

Best Regards,
Ildikó



__
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] [elections] Technical Committee Election Results

2017-10-20 Thread Ildiko Vancsa
Congratulations to our new TC members! :)

Best Regards,
Ildikó


> On 2017. Oct 21., at 1:59, Kendall Nelson  wrote:
> 
> Hello Everyone :) 
> 
> Please join me in congratulating the 6 newly elected members of the Technical 
> Committee (TC)!
> 
> Colleen Murphy (cmurphy)
> Doug Hellmann (dhellmann)
> Emilien Macchi (emilienm)
> Jeremy Stanley (fungi)
> Julia Kreger (TheJulia)
> Paul Belanger (pabelanger)
> 
> Full results: 
> http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ce86063991ef8aae 
> 
> Election process details and results are also available here: 
> https://governance.openstack.org/election/ 
> 
> Thank you to all of the candidates, having a good group of candidates helps 
> engage the community in our democratic process.
> 
> Thank you to all who voted and who encouraged others to vote. We need to 
> ensure your voice is heard.
> 
> Thank you for another great round.
> 
> -Kendall Nelson (diablo_rojo)
> 
> [1] https://review.openstack.org/#/c/513881/ 
> __
> 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][tc] TC Candidates: what does an OpenStack user look like?

2017-10-13 Thread Ildiko Vancsa
Hi Zane,

A few comments in line.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)


> On 2017. Oct 13., at 21:21, Zane Bitter  wrote:
> 
> Replying to myself here, to avoid singling anyone in particular out. I want 
> to rephrase the question, because people are overwhelmingly either failing to 
> understand or refusing to answer it in the way I intended it.

The great thing about this community that it consists of hundreds of 
individuals with their own experiences, expertise and view points. This also 
means that you will get interpretations of and answers to your question that 
reflect those which also helps with observing the problem space from multiple 
aspects to ensure that we come up with a good solution *together* by the end. 
This includes reiterating on the problem as well as it is often hard to express 
it for the first try to include all the aspects that’s required for others to 
interpret it the same way.

> 
> Most of the candidates are essentially saying that the answer is 'everyone'.
> 
> I'm glad that we have such a bunch of next-level geniuses running for the TC 
> that they are able to analyse the needs of all 7 billion people and evaluate 
> every decision they make against all of them in real time. Me, I'm just an 
> ordinary guy who can only hold a few things in his head at once, so I just 
> try to focus on those and collaborate with people who have different 
> perspectives to make sure that a range of needs are covered. This is kind of 
> the founding principle of the Open Source (note: not Free Software) movement, 
> actually. None of us is as smart as all of us (present company excepted, 
> apparently). So it's good, but somewhat surprising that y'all are still here, 
> given that you would be guaranteed insta-billionaires if you went out and 
> started a proprietary software company.
> 
> All sarcasm aside though, 'everyone' is a BS non-answer. It's the 
> politician's answer.

All sarcasm aside, it’s a generic answer to a generic question. On the other 
hand ‘everyone' also represents a mindset of thinking about the aspect that 
someone will use your feature when you design the API to it, which should be a 
starting point and not the failing/ending point of the discussion.

> Not only because engineering trade-offs are a real thing, and some use cases 
> will *definitely* be excluded in order to better serve others, but because 
> the average user doesn't exist. If you design for the 'average' user then you 
> are designing for nobody, because nobody is the average user. We shouldn't be 
> designing for 'everybody' (aka nobody in particular), but for a large variety 
> of somebodies.
> 
> As an example, look at the Keystone discussion that I linked below.
> - If you were designing Keystone for an individual user, you'd might just 
> have one account per tenant.
> - If you were designing Keystone for a team deploying semi-autonomous apps, 
> you might design a way for multiple agents to authenticate to each tenant.
> - If you were designing Keystone for 'everyone', you might have a matrix of 
> users, tenants and roles - the most generic solution, right? - and spend half 
> a decade polishing it without ever realising that individual users don't need 
> it and teams can't use it.
> 
> One of these solutions works for both individuals and teams. The other two 
> only work for individuals. As an added bonus, one of those is also expensive 
> to develop and hard to operate. That's why we should design for someones, not 
> for 'everyone'. This is not a problem limited to Keystone - throughout 
> OpenStack we often fail to develop solutions that can actually be used by the 
> people whom we say we're building them for, IMHO.
> 
> I'm not asking y'all to say that some group of end-users is unimportant even 
> though the question is trying to keep the bar extremely low by asking about 
> only one group. Nor am I asking y'all to say that operators are unimportant, 
> even though the question is *explicitly* *NOT* about operators.
> 
> I'm asking if you can describe, to a modest level of detail, even one *end* 
> user persona for OpenStack that you're familiar enough with to be comfortable 
> advocating for on the TC.

To answer your more specific question, let me pick a Telecom operator to 
advocate for. Please don’t get mislead by the word ‘operator’ here, it is the 
term what the industry uses in that sector and they are representing one group 
of our users.

A Telecom operator has various requirements and challenges when it comes to 
cloud and open source and especially the two together. They are by definition 
looking for a solution that follows standards and guidelines defined by various 
Standards Development Organizations (SDO’s), which already puts a challenge on 
the API design and the people also who do the design and development 
activities. Especially in an open source environment, where let’s face it, we 
usually don’t really care however there are 

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

2017-10-13 Thread Ildiko Vancsa
Hi Flavio,

I would like to refer to another thread about areas the TC should be more 
active in raised by Ed Leafe where trust and mentorship were brought up by a 
few of us.

I think one of the key factors of being open and inclusive is to help and 
mentor new contributors/community members regardless where and who they are.

To mention examples, we have several places around the globe with time zones we 
didn’t necessarily keep in mind in the past or areas where language barriers 
are higher. I think we need to spend time on understanding what the barriers 
might be that keep people back from actively participating in the community 
while we are thinking about actions.

Seeing the activity on the #openstack-tc channel I think that’s a great example 
of how to involve and engage more people in the different discussions by 
removing the dedicated meeting slot and switch to office hours and providing a 
forum where TC members are available to everyone.

We have a new proposal to create a SIG called (something like) 'First Contact 
SIG’. I hope discussions on diversity and inclusiveness will come up there with 
the people who are passionate about on-boarding. As joining an open environment 
can be challenging and intimidating having people who are eager to help visible 
and accessible is crucial.

To the margin, I think on the technology side we are progressing well, so I 
would not reflect on that in this thread.

Thanks and Best Regards,
Ildikó


> On 2017. Oct 13., at 14:45, Flavio Percoco  wrote:
> 
> Greetings,
> 
> Some of you, TC candidates, expressed concerns about diversity and 
> inclusiveness
> (or inclusivity, depending on your taste) in your candidacy. I believe this 
> is a
> broad, and some times ill-used, topic so, I'd like to know, from y'all, how 
> you
> think we could make our community more inclusive. What areas would you improve
> first?
> 
> Thank you,
> Flavio
> 
> --
> @flaper87
> Flavio Percoco
> __
> 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] [tc][election] Question for the candidates

2017-10-13 Thread Ildiko Vancsa
By being involved in training activities and on-boarding new contributors to 
our community I would like to join to Emilien on his point.

I think we have a great, open and welcoming community already, but we still 
have many areas to improve. Teaching the new community members the processes 
and tools is essential and also the easier part.

The difficulty starts when they start to actively contribute to a project and 
they need to understand the mission, scope, architecture and dynamics of it to 
become a team member longer term and take on responsibilities. With smaller 
projects it is usually easier, while the more complex projects can be 
challenging both for the new team members and the core team.

With smaller groups we get back to a discussion periodically about encouraging 
the teams to do more mentoring and also about mentoring the mentors as we have 
a few experienced people and teams with good examples already. In my view the 
TC can help with putting emphasis on encouraging this mentality and direction 
besides looking into metrics.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)


> On 2017. Oct 12., at 23:22, Emilien Macchi  wrote:
> 
> On Thu, Oct 12, 2017 at 11:38 AM, Ed Leafe  wrote:
>> In the past year or so, has there been anything that made you think “I wish 
>> the TC would do something about that!” ? If so, what was it, and what would 
>> you have wanted the TC to do about it?
> 
> I've been part of the TC during the past year (first time) but I still
> have an answer to that question.
> There is one thing I wish the TC would do more is to encourage
> projects to grow and empower trust in certain projects.
> Beside technical things, we want an healthy community and grow
> developer's knowledge so OpenStack can be a better place to
> contribute. I think some projects are doing well but some of them
> might need some mentoring on that front (maybe from some TC members).
> For example, I'm thinking about the way some projects handle core
> reviewers elections and their metrics used to do so. I think the TC
> might ensure that healthy metrics and discussion happen, so projects
> can scale.
> 
> I'm happy to answer questions on that topic.
> 
> Thanks Ed for this first question :-)
> -- 
> 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][tc] TC Candidates: what does an OpenStack user look like?

2017-10-13 Thread Ildiko Vancsa
Hi All,

Let me reflect to the question in the subject first where I would like to stick 
to the word ‘user’ and keep my answer simple. I think an OpenStack user 
is/looks like as an average person.

To give a longer explanation, in my view when we are designing our user-facing 
API’s we need to keep in mind that we don’t know who is going to use them BUT 
let that be an application developer, a researcher or even a person who seeks 
for a place for their IRC-bouncer, so anyone who interacts with them, should be 
equally able to do so without a PhD degree, the history of the development 
process of a particular functionality, without the need to read the code first 
and so forth.

The above statement is applicable in any given period of time, meaning to 
provide a consistent and consistently pleasant and functional environment from 
release to release.

To answer the follow up question on 'Who are _you_ building OpenStack for?’ I 
would mention operators as well, who need to deal with deploying, configuring, 
troubleshooting and managing the daily operational tasks regardless of the 
location, nature and size of an OpenStack deployment.

I think as in many cases when this topic comes up it’s more of a social than a 
technical challenge.

To continue on that aspect, when I’m involved in a feature design and 
development activity I like to imagine that I will be the one, who will operate 
the service and use the newly introduced functionality. It helps much to avoid 
decisions that sacrifices the operator and user experience in favor of faster 
and easier design and implementation. I also like to encourage the fellow 
community members to do the same and also to play with what we are producing to 
get the first hand experience.

If the intention is there and we have the right mindset the technology will 
help us in the technical implications like automation, maintainability, 
complexity, documentation and so forth.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)


> On 2017. Oct 12., at 18:51, Zane Bitter  wrote:
> 
> (Reminder: we are in the TC election campaigning period, and we all have the 
> opportunity to question the candidates. The campaigning period ends on 
> Saturday, so make with the questions.)
> 
> 
> In my head, I have a mental picture of who I'm building OpenStack for. When 
> I'm making design decisions I try to think about how it will affect these 
> hypothetical near-future users. By 'users' here I mean end-users, the actual 
> consumers of OpenStack APIs. What will it enable them to do? What will they 
> have to work around? I think we probably all do this, at least 
> subconsciously. (Free tip: try doing it consciously.)
> 
> So my question to the TC candidates (and incumbent TC members, or anyone 
> else, if they want to answer) is: what does the hypothetical OpenStack user 
> that is top-of-mind in your head look like? Who are _you_ building OpenStack 
> for?
> 
> There's a description of mine in this email, as an example:
> http://lists.openstack.org/pipermail/openstack-dev/2017-October/123312.html
> 
> To be clear, for me at least there's only one wrong answer ("person who needs 
> somewhere to run their IRC bouncer"). What's important in my opinion is that 
> we have a bunch of people with *different* answers on the TC, because I think 
> that will lead to better discussion and hopefully better decisions.
> 
> Discuss.
> 
> cheers,
> Zane.
> 
> __
> 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] [tc][election] Question for the candidates

2017-10-13 Thread Ildiko Vancsa
Hi All,

I agree with the items pointed out in the previous mails in the thread.

In my view the discussion on the vision was crucial in order to synchronize on 
what we think OpenStack is and to understand what direction we would like it to 
move and how we keep it an innovative environment that fits into the ecosystem 
around. It is also important to revisit the mission time to time and shape it 
to how the technology and ecosystem around us evolves.

The discussion about new languages is also pointing towards being inclusive and 
diverse in technology which is a very important step to keep OpenStack current 
and flexible and to support the integration engine nature of it on the way 
forward.

However, to pick my choice, I would like to take a step away from technology 
and mention the decision on dropping the weekly meetings and using the mailing 
list and setting up an IRC channel and office hours for the TC. I think it is 
just as important if not slightly more than the technology itself to be 
critical and innovative with our processes too within the community to ensure 
that we are open and inclusive in practice as well.

This might be one of the reasons to have such good diversity among the 
candidates this time around which shows we are moving to the right direction 
and is also encouraging as we need all the voices and different points of view, 
experience and expertise represented in the technical leadership of our 
community.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)


> On 2017. Oct 13., at 6:49, Swapnil Kulkarni (coolsvap)  
> wrote:
> 
> On Fri, Oct 13, 2017 at 1:12 AM, Clay Gerrard  wrote:
>> I like a representative democracy.  It mostly means I get a say in which
>> other people I have to trust to think deeply about issues which effect me
>> and make decisions which I agree (more or less) are of benefit to the social
>> groups in which I participate.  When I vote IRL I like to consider voting
>> records.  Actions speak louder blah blah.
>> 
>> To candidates:
>> 
>> Would you please self select a change (or changes) from
>> https://github.com/openstack/governance/ in the past ~12 mo or so where they
>> thought the outcome or the discussion/process was particular good and
>> explain why you think so?
>> 
>> It'd be super helpful to me, thanks!
>> 
>> -Clay
>> 
>> __
>> 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
>> 
> 
> I have few of them on my mind.
> 
> Setting up guidelines for managing releases of binary artifacts [1]
> was very important in and key to the hearts of most OpenStack
> operators and everyone who's looking at the next big leap with
> containerized deployment.
> 
> Embracing new languages in OpenStack which are required as dependency
> for certain projects [2] [3] is a very important decision and I would
> really like to see it through. While there is a lot of work to be done
> to get something fully operational in current infrastructure but as we
> will have more contributors who feel the need, we have the background
> work ready for it.
> 
> And of course setting up the vision and mission for TC [4] was one of
> the important things done. There will still be updates to it, but the
> current draft is a piece of work with a diverse community like ours.
> 
> [1] https://review.openstack.org/#/c/469265/
> [2] https://review.openstack.org/#/c/451524/
> [3] https://review.openstack.org/#/c/398875/
> [4] https://review.openstack.org/#/c/453262/
> 
> -- 
> Best Regards,
> Swapnil Kulkarni
> irc : coolsvap
> me at coolsvap dot net
> 
> __
> 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] [os-upstream-institute][all] Looking for mentors for upcoming events

2017-10-09 Thread Ildiko Vancsa
Hi All,

We have two Upstream Institute trainings [1] upcoming and we are looking for 
mentors to join us and help new contributors to start their journey in 
OpenStack.

We have a training in Copenhagen on October 18 and one in Sydney before the 
Summit on November 4-5. If you are available for each or both of these 
occasions and interested to join our crew please sign up on our wiki page [2].

If you have any questions please reply to this thread or reach out to the team 
on the #openstack-upstream-institute IRC channel.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)

[1] https://docs.openstack.org/upstream-training/#upcoming-trainings
[2] https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions
__
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] [os-upstream-institute] Meeting reminder

2017-10-09 Thread Ildiko Vancsa
Hi Training Team,

This is a friendly reminder that we are having our meeting in two hours (2000 
UTC) on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó
__
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] [tc][election] TC candidacy

2017-10-09 Thread Ildiko Vancsa
Hi All,

I would like to announce my candidacy for a seat on the OpenStack Technical
Committee for the upcoming year.

I'm working for the OpenStack Foundation as Ecosystem Technical Lead where
my responsibility is to help our members to succeed with OpenStack both as
software and community. My main focus areas are Telecom/NFV, on boarding
and collaboration with adjacent communities.

I joined the community nearly four years ago. By my contributions I’m the 
constant
voice of usability and maintainability aspects while encouraging collaboration 
within
and between project teams.

During the past few years I’ve been leading the activities to add the Cinder 
volume
multi-attach functionality to Nova, which turned into a collaborative activity 
between
the two teams to simplify the interaction between the two services [1]. By this 
work
we are increasing maintainability of the code bases and stability of the 
services.
Driven by the experiences of this work I see cross-project collaboration as an 
area
to further improve. As part of the TC I would like to continue driving 
cross-project
activities, where I would like to help with making the interactions between the 
teams
more efficient to ensure end-to-end feature implementation and continuous code
maintenance and improvement.

I’m one of the drivers of the Upstream Institute activities to provide guidance 
to
newcomers to the community. As our community is a continuously changing
environment it is crucial to be welcoming and ensure we distribute the knowledge
about our processes and code base while remaining open to transfer 
responsibilities
to newer community members. As a TC member I would like to help the project
teams to share and maintain this mindset to help the contributor ecosystem to
remain healthy and balanced and our teams to become more efficient.

In the course of my current role within the Foundation I continuously learn 
about the
goals and challenges of our ecosystem companies who are productifying, 
distributing
and operating OpenStack. It is very important to keep a close feedback loop 
between
our users, operators and developers in order to define our focus and priorities 
to features
requests and issues that are in high demand. At the same time it is also 
crucial to keep
OpenStack an innovative environment which is open to explore new emerging 
technologies
and also integrates well with other communities in the ecosystem. If I get 
elected to the
TC I would like to help collaborating with organizations on different fields, 
from
standardization (i.e. ETSI NFV) through SDN/NFV (i.e. OPNFV) to the research and
scientific area.

As an example I’ve been involved in OPNFV [2] for about two and a half years 
and I’m
also one of their ambassadors [3]. I’m continuously working on to find the 
connection
points between the two communities [4] to build a large ecosystem which fits 
OpenStack's
current priorities in the sense of actively supporting and being the foundation 
for NFV. As
part of the TC I would like to continue to help the ongoing joint activities to 
create
an interoperability test suite for the NFV area and have OPNFV’s CI system 
integrated
with OpenStack to get close to immediate feedback while developing new Telecom
and NFV related features. As the adoption of OpenStack in the Telecom area is
continuously growing and operators are looking at OpenStack as a main building
block for their systems, I would like to serve as a representative in the 
technical
driving force of OpenStack, who can operate as a translator to build a common
roadmap.

Last but not least, I would like to increase diversity in the TC, but more 
importantly
my goal is to add fresh blood to the group driving this community. In my
opinion it is crucial to constantly revisit items from a different perspective 
and
let new voices articulate their views and ideas in order to see the big 
picture. Long
term this can ensure that OpenStack keeps its adaptability to continue to be a
smoothly functioning ecosystem providing a stable, successful and continuously
evolving software package.

Thank you for reading through my thoughts. It is an honor to be part of 
OpenStack,
which is why I would like to take part in helping to further the efforts of 
providing a
package that can serve the whole industry and which is backed up by a growing
and smoothly functioning ecosystem.

Thank you for your consideration.

Best Regards,
Ildikó (ildikov)

[1] http://stackalytics.com/?release=all_id=ildiko-vancsa=person-day
[2] https://www.opnfv.org
[3] https://www.opnfv.org/community/ambassadors
[4] https://www.openstack.org/summit/austin-2016/summit-schedule/events/7510


__
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] [os-upstream-institute] Meeting reminder

2017-10-03 Thread Ildiko Vancsa
Hi Training Team,

This is a friendly reminder that we are having our meeting in 15 minutes (0900 
UTC) on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó
__
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] Garbage patches for simple typo fixes

2017-09-23 Thread Ildiko Vancsa

> On 2017. Sep 23., at 9:11, Doug Hellmann  wrote:
> 
> Excerpts from Huang Zhiteng's message of 2017-09-23 10:00:00 +0800:
>> On Sat, Sep 23, 2017 at 8:34 AM, Zhipeng Huang  wrote:
>>> Hi Paul,
>>> 
>>> Unfortunately I know better on this matter and it is not the matter of topic
>>> dispute as many people on this thread who has been disturbed and annoyed by
>>> the padding/trolling.
>>> 
>>> So yes I'm sticking with stupid because it hurts the OpenStack community as
>>> a whole and hurts the reputation of the dev community from my country which
>>> in large are great people with good hearts and skills.
>>> 
>>> I'm not giving even an inch of the benefit of doubt to these padding
>>> activities and people behind it.
>> Hi Zhipeng,
>> 
>> Not sure how much you have been involved in the dev community in
>> China, but it's now a good time to talk to those companies (in public
>> or private) and ask them to stop encourage their developers to submit
>> such changes.
> 
> I would prefer to set up a system where we can have those sorts of
> conversations in private, to encourage people to contribute
> constructively instead of shaming them.
> 
> Doug

+1, I completely agree.

In my earlier experience with this the main reason for this behavior to happen 
is the lack of experience with the tools and the open source environment and 
ways of working. As we are working with people all around the globe we also 
need to take into consideration the different cultures and how they communicate 
and handle situations like this.

We should put emphasis on remaining an open, friendly and diverse community by 
providing education and help to those people who need it the best way we can. 
And this should include not assuming the worse before we actually know why 
things happened and not publicly shaming people, but to provide mentorship.

I think this is extremely important, and I’m happy to be a ‘go to person’ and 
help people understand how these systems work and what is the best way to join 
an open source community like OpenStack in case you need more people to get 
involved in communicating our principles.

Thanks,
Ildikó
IRC: ildikov


> 
>> 
>>> 
>>> 
>>> On Sat, Sep 23, 2017 at 8:16 AM, Paul Belanger 
>>> wrote:
 
 On Fri, Sep 22, 2017 at 10:26:09AM +0800, Zhipeng Huang wrote:
> Let's not forget the epic fail earlier on the "contribution.rst fix"
> that
> almost melt down the community CI system.
> 
> For any companies that are doing what Matt mentioned, please be aware
> that
> the dev community of the country you belong to is getting hurt by your
> stupid activity.
> 
> Stop patch trolling and doing something meaningful.
> 
 Sorry, but I found this comment over the line. Just because you disagree
 with
 the $topic at hand, doesn't mean you should default to calling it
 'stupid'. Give
 somebody the benefit of not knowing any better.
 
 This is not a good example of encouraging anybody to contribute to the
 project.
 
 -Paul
 
> On Fri, Sep 22, 2017 at 10:21 AM, Matt Riedemann 
> wrote:
> 
>> I just wanted to highlight to people that there seems to be a series
>> of
>> garbage patches in various projects [1] which are basically doing
>> things
>> like fixing a single typo in a code comment, or very narrowly changing
>> http
>> to https in links within docs.
>> 
>> Also +1ing ones own changes.
>> 
>> I've been trying to snuff these out in nova, but I see it's basically
>> a
>> pattern widespread across several projects.
>> 
>> This is the boilerplate comment I give with my -1, feel free to employ
>> it
>> yourself.
>> 
>> "Sorry but this isn't really a useful change. Fixing typos in code
>> comments when the context is still clear doesn't really help us, and
>> mostly
>> seems like looking for padding stats on stackalytics. It's also a
>> drain on
>> our CI environment.
>> 
>> If you fixed all of the typos in a single module, or in user-facing
>> documentation, or error messages, or something in the logs, or
>> something
>> that actually doesn't make sense in code comments, then maybe, but
>> this
>> isn't one of those things."
>> 
>> I'm not trying to be a jerk here, but this is annoying to the point I
>> felt
>> the need to say something publicly.
>> 
>> [1] https://review.openstack.org/#/q/author:%255E.*inspur.*
>> 
>> --
>> 
>> Thanks,
>> 
>> Matt
>> 
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 

Re: [openstack-dev] Garbage patches for simple typo fixes

2017-09-22 Thread Ildiko Vancsa
Hi All,

Another forum we try to put emphasis on this is the Upstream Institute 
trainings we have before the Summits and on some smaller events as well.

We usually try to spend some quality time on review best practices and on 
metrics as well. The aim is to make people realize that if they need practice 
with the process the project repositories are not the place for that and also 
to let them know that we see the patterns and they get negative recognition for 
it.

The only issue with that is I’m not sure we always have the right audience, 
like people might not contribute after all neither they give the knowledge and 
heads up to their colleagues in the company who do. :( Regardless of this we 
will continue to highlight these and if you have suggestion on what else we 
should mention or how to better articulate it we are open to ideas.

We were also thinking about collecting ideas and suggestions for people who 
would take on mentoring in projects, like what and how to do. Do you see this 
activity being part of that too? Could we say something like if we have a few 
people per project who are willing to coach and mentor people we can have a 
small set of guidelines for them on how to start the communication for these 
cases? Or would this rather be handled centrally?

As for those who are practicing we have sandbox repositories/projects in all 
the tools which might worth highlighting.

The new Contributor Portal can also be a good place to highlight corresponding 
best practices and point out behaviors we disagree with.

Thanks,
Ildikó
IRC: ildikov


> On 2017. Sep 22., at 12:47, Doug Hellmann  wrote:
> 
> Excerpts from Davanum Srinivas (dims)'s message of 2017-09-22 13:47:06 -0400:
>> Doug,
>> Howard (cc'ed) already did a bunch of reaching out especially on
>> wechat. We should request his help.
>> 
>> Howard,
>> Can you please help with communications and follow up?
>> 
>> Thanks,
>> Dims
> 
> Thanks, Dims and Howard,
> 
> I think the problem has reached a point where it would be a good
> idea to formalize our approach to outreach. We should track the
> patches or patch series identified as problematic, so reviewers
> know not to bother with them. We can also track who is contacting
> whom (and how) so we don't have a bunch of people replicating work
> or causing confusion for people who are trying to contribute. Having
> that information will also help us figure out when we need to
> escalate by finding the right managers to be talking to.
> 
> Let's put together a small team to manage this instead of letting
> it continue to cause frustration for everyone.
> 
> Doug
> 
>> 
>> On Fri, Sep 22, 2017 at 1:43 PM, Doug Hellmann  wrote:
>>> Excerpts from Matt Riedemann's message of 2017-09-22 08:26:31 -0500:
 On 9/22/2017 7:10 AM, Tom Barron wrote:
> FWIW I think it is better not to attribute motivation in these cases.
> Perhaps the code submitter is trying to pad stats, but perhaps they are
> just a new contributor trying to learn the process with a "harmless"
> patch, or just a compulsive clean-upper who hasn't thought through the
> costs in reviewer time and CI resources.
 
 I agree. However, the one that set me off last night was a person from
 one company who I've repeatedly -1ed the same types of patches in nova
 for weeks, including on stable branches, and within 10 minutes of each
 other across several repos, so it's clearly part of some daily routine.
 That's what prompted me to send something to the mailing list.
 
>>> 
>>> As fungi points out, education and communication are likely to be
>>> our best solution. Maybe one approach is to identify the companies
>>> and individuals involved and find one of our community members to
>>> contact them directly via email.  We would want the person doing
>>> that to be willing to explain all of the reasons the community does
>>> not want the sort of activity we are rejecting and to provide
>>> guidance about more useful contributions (Matt's comment is a great
>>> start on both). I imagine that conversation would take a good deal
>>> of patience, especially after the second or third time, but a personal
>>> touch frequently makes all the difference in these sorts of cases.
>>> 
>>> If we have someone willing to step into that sort of role, I would
>>> be happy to help craft the initial contact messages and advise as
>>> needed.
>>> 
>>> Does anyone want to volunteer to work with me and actually send the
>>> emails?
>>> 
>>> 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 

[openstack-dev] [os-upstream-institute] This week's meeting is cancelled

2017-09-18 Thread Ildiko Vancsa
Hi Training Team,

I hope all of you who attended the PTG had a good time and got home safe.

I’m out of timezone this week therefore this week’s meeting is cancelled.

As a reminder, we have upcoming training occasions in London (Sept. 26), 
Copenhagen (Oct. 18) and Sydney (Nov. 4-5). Please sign up on the staff wiki 
page if you can come and help out on any of these events: 
https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions

And also keep an eye on the open reviews: 
https://review.openstack.org/#/q/project:openstack/training-guides+status:open 
:)

Thanks,
Ildikó
(IRC: ildikov)
__
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] [os-upstream-institute][all] Get together at the PTG

2017-09-11 Thread Ildiko Vancsa
Hi All,,

Friendly reminder that we meet __tomorrow (Tuesday, Sept. 12)__ at __lunch time 
(12pm)__. :)

Look for the __reserved signs at the back of the lunch seating room__. Please 
grab your food and then we will have lunch together and discuss what events we 
have coming up and what we would like to achieve for each and any topics that 
come to our mind during the hour.

I would like to also encourage everyone who’s not participating in this 
activity yet, but would be interested to meet us and join to come and have 
lunch with us.

Looking forward to seeing you all tomorrow!
Thanks and Best Regards,
Ildikó
(IRC: ildikov)


> On 2017. Sep 4., at 17:34, Ildiko Vancsa <ildiko.van...@gmail.com> wrote:
> 
> Hi All,
> 
> Thank you for responding, we have the day for the gathering, which is next 
> Tuesday (September 12).
> 
> As we all have different responsibilities through the day and different 
> sessions to attend we will try and have a lunch meeting as we had on the 
> previous PTG. Please follow the mailing list for update on exact time and 
> location.
> 
> Safe travels and see you next week!
> 
> Thanks and Best Regards,
> Ildikó
> (IRC: ildikov)
> 
> 
>> On 2017. Aug 28., at 17:52, Jay S Bryant <jungleb...@gmail.com> wrote:
>> 
>> Ildiko,
>> 
>> Thanks for setting this up.  I will be there and would love to join.  I too 
>> have more flexibility on Monday and Tuesday.
>> 
>> Thanks!
>> 
>> Jay
>> 
>> 
>> 
>> On 8/25/2017 9:36 AM, Ildiko Vancsa wrote:
>>> Hi Training Team and All,
>>> 
>>> As we have our next PTG coming up shortly I think that would be a great 
>>> opportunity for the team and everyone who’s interested to meet and check 
>>> where we are and what our future plans are. :)
>>> 
>>> I would like to ask you to raise your hand by replying to this mail if you 
>>> will be around during the PTG week in Denver and would be interested in 
>>> joining. Please also indicate your availability for the week.
>>> 
>>> Based on the responses we will pick a day and a time that works best for 
>>> most to have our gathering.
>>> 
>>> Please let me know if you have any questions.
>>> 
>>> Thanks and Best Regards,
>>> Ildikó
>>> (IRC: ildikov)
>>> 
>>> 
>>> 
>>> __
>>> 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


Re: [openstack-dev] [os-upstream-institute][all] Get together at the PTG

2017-09-04 Thread Ildiko Vancsa
Hi All,

Thank you for responding, we have the day for the gathering, which is next 
Tuesday (September 12).

As we all have different responsibilities through the day and different 
sessions to attend we will try and have a lunch meeting as we had on the 
previous PTG. Please follow the mailing list for update on exact time and 
location.

Safe travels and see you next week!

Thanks and Best Regards,
Ildikó
(IRC: ildikov)


> On 2017. Aug 28., at 17:52, Jay S Bryant <jungleb...@gmail.com> wrote:
> 
> Ildiko,
> 
> Thanks for setting this up.  I will be there and would love to join.  I too 
> have more flexibility on Monday and Tuesday.
> 
> Thanks!
> 
> Jay
> 
> 
> 
> On 8/25/2017 9:36 AM, Ildiko Vancsa wrote:
>> Hi Training Team and All,
>> 
>> As we have our next PTG coming up shortly I think that would be a great 
>> opportunity for the team and everyone who’s interested to meet and check 
>> where we are and what our future plans are. :)
>> 
>> I would like to ask you to raise your hand by replying to this mail if you 
>> will be around during the PTG week in Denver and would be interested in 
>> joining. Please also indicate your availability for the week.
>> 
>> Based on the responses we will pick a day and a time that works best for 
>> most to have our gathering.
>> 
>> Please let me know if you have any questions.
>> 
>> Thanks and Best Regards,
>> Ildikó
>> (IRC: ildikov)
>> 
>> 
>> 
>> __
>> 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-dev] [os-upstream-institute] This week's and next week's meeting is canceled

2017-09-04 Thread Ildiko Vancsa
Hi Training Team,

This week’s meeting is canceled, let’s sync up over e-mail and on the IRC 
channel and hopefully see most of you at the PTG next week.

We’ve just updated the index page on the web to make it less crowded and more 
readable, take a look: https://docs.openstack.org/upstream-training/

Please also take a look at the upcoming occasions and raise your hand if you’re 
available for either of those!

The ongoing activities are:

* Adding tags to the material
  * https://etherpad.openstack.org/p/OUI_Module_tags
  * https://review.openstack.org/#/c/496425/
* Mark is working on improving the VM image, which needs testing
* General material update with the intention to make it as modular as possible

Thanks,
Ildikó
(IRC: ildikov)
__
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] [os-upstream-institute] Meeting reminder

2017-08-28 Thread Ildiko Vancsa
Hi Training Team,

This is a friendly reminder that we are having our meeting in less than an hour 
(2000 UTC) on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó
__
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] [os-upstream-institute][all] Get together at the PTG

2017-08-25 Thread Ildiko Vancsa
Hi Training Team and All,

As we have our next PTG coming up shortly I think that would be a great 
opportunity for the team and everyone who’s interested to meet and check where 
we are and what our future plans are. :)

I would like to ask you to raise your hand by replying to this mail if you will 
be around during the PTG week in Denver and would be interested in joining. 
Please also indicate your availability for the week.

Based on the responses we will pick a day and a time that works best for most 
to have our gathering.

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)



__
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] [os-upstream-institute] Meeting reminder

2017-08-22 Thread Ildiko Vancsa
Hi Training Team,

This is a friendly reminder that we are having our meeting in 90 minutes (0900 
UTC) on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó
__
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] [os-upstream-institute]Review tag proposals for the training slides

2017-08-14 Thread Ildiko Vancsa
Hi Training Team and All,

We decided to add tagging to our slide material to make it easier to utilize 
the modular structure of the training even more.

We would like to add indications to the training modules and exercises on who 
would be the target audience, whether we recommend the block as part of a 
shorter training or rather to fit into a longer one and so forth.

We will list the tags with a short description on the training web page and add 
use them with the material.

We created an etherpad to agree on a base set of tags we are going to start to 
use: https://etherpad.openstack.org/p/OUI_Module_tags

Please review the current proposals and add comments, questions, +1’s and/or 
new items to the list and do all this __by next Monday, (21st of August)__.

Please let me know if you have any questions about the tags overall.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)
__
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] [os-upstream-institute] Meeting reminder

2017-08-14 Thread Ildiko Vancsa
Hi Training Team,

This is a friendly reminder that we are having our meeting in a bit (2000 UTC) 
on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó
__
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] [os-upstream-institute] Meeting reminder

2017-08-08 Thread Ildiko Vancsa
Hi Training Team,

This is a friendly reminder that this week’s meeting is in one and a half hours 
at 0900 UTC on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you on the meeting soon! :)

Thanks and Best Regards,
Ildikó



__
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] ETSI NFV - OpenStack workshop in Denver

2017-08-07 Thread Ildiko Vancsa
Hi All,

I would like to draw your attention to a co-located event during the upcoming 
OpenStack PTG in Denver. The event will take place in the OpenStack PTG venue 
(Renaissance Hotel, Denver) at 2pm - 5pm on Tuesday (Sept. 12).

The workshop intends to provide a forum to identify and discuss the common use 
cases and tasks between OpenStack and ETSI NFV and take these items to the next 
level. The co-located workshop will be a working event to discuss the gaps and 
requirements on both sides in details and work on the technical solutions and 
next steps.

You can find more details and planned agenda on the following etherpad: 
https://etherpad.openstack.org/p/etsi-nfv-openstack-gathering-denver

Please add your name to the etherpad if you intend to join. If you have any 
questions or comments feel free to add them to the etherpad or reply to this 
mail thread.

Thanks and Best Regards,
Ildikó



__
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] Fwd: ETSI NFV - OpenStack PTG in Denver

2017-08-02 Thread Ildiko Vancsa
Hi All,

I was kindly asked by Tetsuya (in cc) to help him distribute the information 
about an ETSI NFV tutorial & workshop that might be relevant to your work and 
therefore you might be interested in joining.

You can find more information on the wiki page linked below.

Please reach out to Tetsuya or respond to this mail thread in case you have any 
questions.

Thanks and Best Regards,
Ildikó


> Begin forwarded message:
> 
> Dear OpenStack folks,
> 
> Let me introduce the ETSI NFV Tutorial & Specfest(Hackfest) event on 
> September 11th in Denver downtown. 
> 
> During the ETSI NFV-ISG meeting in Denver, we would plan a special tutorial & 
> specfest event on Monday, September 11th, which introduces and hacks on the 
> latest ETSI NFV API specifications, VNF Package, Descriptors, OpenAPI, etc. 
> Anyone can join the event without registration to the ETSI NFV meeting. It is 
> free of charge. The details are in the ETSI NFV public wiki page:
> https://nfvwiki.etsi.org/index.php?title=ETSI_NFV_Tutorial
> 
> Please come and join. 
> 
> Best Regards,
> Tetsuya Nakamura, CableLabs,
> Vice Chair, ETSI NFV-ISG,
> t.nakam...@cablelabs.com
> 


__
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] [os-upstream-institute] Meeting reminder

2017-07-31 Thread Ildiko Vancsa
Hi Training Team,

This is a friendly reminder that we are having our meeting in less than an hour 
(2000 UTC) on #openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you soon! :)

Thanks,
Ildikó



__
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] [os-upstream-institute] No meeting on Monday (July 3)

2017-06-30 Thread Ildiko Vancsa
Hi Training Team,

It is a reminder that we are canceling the meeting next Monday (July 3) due to 
the holiday in the US.

The next meeting is on Tuesday, July 10, 0900 UTC on #openstack-mmeting-3. The 
next US friendly time slot is July 17, 2000 UTC.

Have a good (long) weekend! :)

Best Regards,
Ildikó
__
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] [os-upstream-institute] Meeting on the top of the hour

2017-06-27 Thread Ildiko Vancsa
Hi Training Team,

It is a friendly reminder that we’re having our Europe and Asia TZ friendly 
meeting slot at 0900 UTC today, on #openstack-meeting-3.

You can find the meeting agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

Thanks,
Ildikó
(IRC: ildikov)
__
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] [os-upstream-institute] Meeting reminder

2017-06-12 Thread Ildiko Vancsa
Hi Training Team,

This is a friendly reminder to have our first meeting in the new alternating 
time slot.

The meeting will take place tomorrow (Tuesday, June 13) at 0900 UTC on 
#openstack-meeting-3.

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings

See you tomorrow on IRC! :)

Thanks and Best Regards,
Ildikó



__
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] [os-upstream-institute] Alternating meeting slot

2017-06-06 Thread Ildiko Vancsa
Hi Training Team,

As we have many team members from Europe and Asia we are now switching to 
alternating meeting slots [1] starting from next week.

On even weeks our meeting slot is 0900 UTC on Tuesdays, while on odd weeks it’s 
2000 UTC on Mondays, all on #openstack-meeting-3.

Our meeting next meeting will be on next Tuesday (June 13) at 0900 UTC on the 
#openstack-meeting-3 channel.

Thanks,
Ildikó

[1] http://eavesdrop.openstack.org/#OpenStack_Upstream_Institute


__
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] [os-upstream-institute] Today's meeting is CANCELED

2017-05-29 Thread Ildiko Vancsa
Hi Team,

Due to the holiday today in the US today’s meeting is canceled.

See you next Monday (June 5th), 2000 UTC on #openstack-meeting-3.

Thanks,
Ildikó
__
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] [os-upstream-institute] Alternating meeting time poll

2017-05-24 Thread Ildiko Vancsa
Hi,

As we are over the Boston training now we can revise a bit how our team 
operates and make improvements.

One area is certainly the meetings as we only have one dedicated meeting slot, 
but team members all around the globe, so we decided to try to continue with 
alternating slots.

If you are already a team member or interested in joining and participating in 
our weekly meetings, and you’re located in the above areas, please fill out 
this poll: https://doodle.com/poll/dmyrf72wfnrp7e5m

The poll is in __UTC__ and please __avoid the dates__ and fill it out 
considering your __general__ availability. The poll contains primarily Europe 
and Asia friendly slots.

If you have any questions or comments please let me know.

Thanks and Best Regards,
Ildikó
__
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] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Ildiko Vancsa
Hi Alex,

First of all thank you for writing this up the summary and list options with 
their expected impacts.

> 
> 1. We could combine all of the documentation builds, so that each project has 
> a single doc/source directory that includes developer, contributor, and user 
> documentation. This option would reduce the number of build jobs we have to 
> run, and cut down on the number of separate sphinx configurations in each 
> repository. It would completely change the way we publish the results, 
> though, and we would need to set up redirects from all of the existing 
> locations to the new locations and move all of the existing documentation 
> under the new structure.
> 
> 2. We could retain the existing trees for developer and API docs, and add a 
> new one for "user" documentation. The installation guide, configuration 
> guide, and admin guide would move here for all projects. Neutron's user 
> documentation would include the current networking guide as well. This option 
> would add 1 new build to each repository, but would allow us to easily roll 
> out the change with less disruption in the way the site is organized and 
> published, so there would be less work in the short term.

I’m fully in favor for option #1 and/or option #2. From the perspective of 
trying to move step-by-step and give a chance to project teams to acclimatize 
with the changes I think starting with #2 should be sufficient.

Although if we think that option #1 is doable as a starting point and also end 
goal, you have my support for that too.

> 
> 3. We could do option 2, but use a separate repository for the new 
> user-oriented documentation. This would allow project teams to delegate 
> management of the documentation to a separate review project-sub-team, but 
> would complicate the process of landing code and documentation updates 
> together so that the docs are always up to date. 
> 

As being one of the advocates on having the documentation living together with 
the code so we can give a chance to the experts of the code changes to add the 
corresponding documentation as well, I'm definitely against option #3. :)

Thanks and Best Regards,
Ildikó
__
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] [doc][ptls][all] Documentation publishing future

2017-05-23 Thread Ildiko Vancsa

> On 2017. May 23., at 15:43, Sean McGinnis  wrote:
> 
> On Mon, May 22, 2017 at 05:50:50PM -0500, Anne Gentle wrote:
>> On Mon, May 22, 2017 at 5:41 PM, Sean McGinnis 
>> wrote:
>> 
>>> 
>>> [snip]
>>> 
>> 
>> Hey Sean, is the "right to merge" the top difficulty you envision with 1 or
>> 2? Or is it finding people to do the writing and reviews? Curious about
>> your thoughts and if you have some experience with specific day-to-day
>> behavior here, I would love your insights.
>> 
>> Anne
> 
> I think it's more about finding people to do the writing and reviews, though
> having incentives like having more say in that area of things could be
> beneficial for finding those people.

I think it is important to note here that by having the documentation (in it’s 
easily identifiable, own folder) living together with the code in the same 
repository you have the developer(s) of the feature as first line candidates on 
adding documentation to their change.

I know that writing good technical documentation is it’s own profession, but 
having the initial data there which can be fixed by experienced writers if 
needed is a huge win compared to anything separated, where you might not have 
any documentation at all.

So by having the ability to -1 a change because of the lack of documentation is 
on one hand might be a process change for reviewers, but gives you the docs 
contributors as well.

So to summarize, the changes what Alex described do not indicate that the core 
team has to write the documentation themselves or finding a team of technical 
writers before applying the changes, but be conscious about caring whether docs 
is added along with the code changes.

Thanks,
Ildikó



__
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] [os-upstream-institute] Meeting reminder :)

2017-05-22 Thread Ildiko Vancsa
Hi Team,

It is a friendly reminder that we have our meeting in less than an hour (2000 
UTC) on #openstack-meeting-3. :)

You can find the agenda here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings 
 

See you there soon!

Thanks,
Ildikó
IRC: ildikov__
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] [os-upstream-institute] Meeting reminder

2017-05-15 Thread Ildiko Vancsa
Hi Training Team,

Just a quick reminder that we have our meeting in ten minutes on 
#openstack-meeting-3.

We will mainly focus on retrospectives from the training in Boston a week ago. 
We have an etherpad with some thoughts already: 
https://etherpad.openstack.org/p/BOS_OUI_Post_Mortem 

Thanks,
Ildikó
__
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] [os-upstream-institute] Meeting reminder

2017-05-01 Thread Ildiko Vancsa
Hi Training Team,

Friendly reminder that we will have our next (and last before the Boston 
training) meeting in less than an hour at 2000 UTC on #openstack-meeting-3.

You can find the agenda for the meeting here: 
https://etherpad.openstack.org/p/openstack-upstream-institute-meetings 


Thanks and Best Regards,
Ildikó__
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] [docs] OpenStack documentation: Forum session

2017-04-28 Thread Ildiko Vancsa
Hi All,

I’m reaching out to you to draw your attention to a Forum topic we proposed 
with Alex (OpenStack Manuals PTL): 
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18939/openstack-documentation-the-future-depends-on-all-of-us
 


As the documentation team is heavily affected by the OSIC news we are looking 
for more involvement from both our user and developer community. The 
documentation team is looking for new contributors and also options to 
restructure some of the guides and how the team operates.

Considering the importance of good and reliable documentation we hope to have 
many of you joining us on Monday in Boston. You can add ideas or questions to 
the Forum etherpad to help us prepare: 
https://etherpad.openstack.org/p/doc-future 
 

If you have any questions or comments in advance please respond to this thread 
or reach out to me (IRC: ildikov) or Alex (IRC: asettle).

Thanks and Best Regards,
Ildikó & Alex__
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] [os-upstream-institute] Meeting reminder

2017-04-24 Thread Ildiko Vancsa
Hi Team,

A friendly reminder that the next meeting is within an hour at 2000 UTC on the 
#openstack-meeting-3 channel. See you there soon! :)

Thanks,
Ildikó
IRC: ildikov



__
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] [os-upstream-institute] Training slot presenter sign-up

2017-04-21 Thread Ildiko Vancsa
Hi Team, :)

As agreed on this week’s meeting I created an etherpad for presenter sign up: 
https://etherpad.openstack.org/p/boston-upstream-institute-presenters 


Please choose the session(s) you would like to teach to the students and add 
your name to it on the etherpad above. If you have any questions or comments 
just reply to this thread or find us on #openstack-upstream-institute.

Some of the most recent changes to a few sections are still on review, so go 
and check them out: 
https://review.openstack.org/#/q/project:openstack/training-guides 
 

Thanks and Best Regards,
Ildikó
IRC: ildikov / coffee_cat__
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] [tc][elections]questions about one platform vision

2017-04-17 Thread Ildiko Vancsa

> On 2017. Apr 16., at 3:03, Neil Jerram  wrote:
> 
> FWIW, I think the Lego analogy is not actually helpful for another reason: it 
> has vastly too many ways of combining, and (hence) no sense at all of 
> consistency / interoperability between the different things that you can 
> construct with it. Whereas for OpenStack I believe you are also aiming for 
> some forms of consistency and interoperability. 

I see your point here and without being too biased by the Lego analogy I don’t 
fully agree.

On one hand, in my view we can go deep and associate to the new style Legos 
where you can build more realistic things and you have more specific pieces and 
not just the plain colored rectangular ones and can explore all the ways of 
putting them together, but I don’t think we want to do that when we are looking 
for some kind of an analogy to help people digest a new concept. We will not 
find anything that will be perfect, I think we only need a good enough one let 
that be Legos or something else.

On the other hand despite of the many ways to combine the Lego blocks you will 
still find matching things, like the ability of attaching the Lego figures for 
instance. In this sense I think we need to find the right level of 
consistency/interoperability here. Like for instance the characteristics and 
requirements of an HPC and a Telecom cloud are different and I don’t think 
there are many use cases to ever connect these two types of clouds or migrate 
workload between them, but there’s still a subset of functionality that both 
areas expect from their OpenStack based cloud, which are really the basics and 
not every small detail.

What the Lego analogy describes well is the consistency between the building 
blocks, which is a really important message in my opinion.

With that being said, if we can find a better one or decide not to use any 
analogies that also works for me. I don't think we should spend overly too much 
time with this, although if we can find a good enough one, I’m in favor to use 
it as it sometimes makes it much easier to get to know and accept a new(-ish) 
concept.

Thanks,
Ildikó


__
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] [os-upstream-institute] Meeting reminder

2017-04-17 Thread Ildiko Vancsa
Hi Team,

A quick reminder that our next meeting will take place in #openstack-meeting-3 
in 15 minutes (2000 UTC). See you there! :)

Thanks,
Ildikó
IRC: ildikov
__
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] [tc][elections]questions about one platform vision

2017-04-13 Thread Ildiko Vancsa

> +1 for us to publish sets of projects that work together for specific
> scenarios. I heard this idea first from Allison Randall and it
> immediately struck a chord. To be fair folks like Jay Pipes have
> always said (paraphrasing) "OpenStack is a toolbox". So it's the next
> step i guess. Lauren Sell was mentioning yesterday about hearing
> confusion around "Big Tent", i do feel that when we put forth a set of
> constellations we can start deprecating the "Big Tent" terminology if
> appropriate.

I think what we are missing here is more of guidelines and more examples to 
give ideas how to build a platform from the blocks. I see “Big Tent” as a 
terminology that covers our governance as well, therefore I would not go that 
far to deprecate it as of now.

On the other hand, I know at least one other community where a very similar 
concept than the set of constellations here is causing just as much frustration 
as the “Big Tent” currently in our case. I think we need to improve on 
communication and guidance first regardless of whether we get to the conclusion 
of changing the terminology finally or not.

Thanks,
Ildikó


__
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] [tc][elections]questions about one platform vision

2017-04-13 Thread Ildiko Vancsa
> […]
> What's the one platform will be in your own words? What's your proposal and 
> your focus to help one platform vision being achieved?

In my view it means that OpenStack contains the blocks to build platforms that 
can serve as a base for different use cases and workloads. We need to keep the 
API’s consistent and the interfaces between the services well defined and 
stable.

In addition, for me, one platform on high level means enablement, flexibility, 
consciousness about the needs of the industry and support of the integration 
points towards related projects/technologies. We need OpenStack to be modular 
with clear communication about the purpose of each service and guidance on how 
to build a platform by using them as Lego pieces, like how you have sample 
photos on the side of the box to give you ideas on what you might want.

I think if we can achieve people seeing OpenStack as a box of Lego, tools, you 
name it, that enables them to build what they need as a base platform to run 
their applications on top we are on the right track. This needs good design, 
consistency and clear communication.

Thanks,
Ildikó


> 
> Best Regards
> Chaoyi Huang (joehuang)
> __
> 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] [tc][election] Questions for Candidates

2017-04-13 Thread Ildiko Vancsa

> You all have proven yourselves to be crucial parts of the community and I 
> just wanted to say good luck to each one of you in the upcoming election!

Thank you. :)

> -What is one trait you have that makes it difficult to work in groups like 
> the TC and how do you counteract it? 

I can be too obsessed with the ‘big picture’ and get distracted by it when it 
comes to details and defining the next steps. While it is very important to 
keep in mind, I need to learn to map it to practical actions in a faster and 
more efficient way.

Being aware of and conscious about our own weaknesses and take steps to improve 
them is crucial, but it is also what makes the TC a diverse group. In my view 
many of the traits mentioned in this thread are traits for the individuals but 
become strength for the group when it operates as a team by having the broad, 
strategic view, the technical depth and the awareness of new and emerging 
technologies all represented and being part of the decision making.

> - What do you see as the biggest roadblock in the upcoming releases for the 
> TC?

For me it is finding the balance, as making OpenStack an innovative and 
continuously evolving environment while keeping the software stable and 
flexible within all the circumstances mentioned in this thread is challenging. 
We need to keep moving away from the perception that OpenStack is a large, 
monolithic software package and help our users and operators to find the best 
setup that fulfills their needs. In addition we should be more open to provide 
the space and opportunity to people to experiment with their ideas, let that be 
new functionality or an attempt to improve something existing.

Reflecting back to what Thierry mentioned about involving our users and 
operators more, I think that would help with the aforementioned challenges and 
points towards a more balanced environment. I would mention Telecom operators 
as an area where we have good examples to community involvement already and I 
get more and more questions about how our community works and how operators 
could get more involved. As these companies are sometimes new to open source 
they need help from us in order to take the next steps and succeed.

> And one lighthearted question: 
> 
> -What is your favorite thing about OpenStack? 

My favorite thing is to feel extremely lucky every day to be part of it! :)

This community made me a better person by becoming more optimistic, 
collaborative and forward looking. It is of course the people who build this 
amazing environment where I found friends, mentors and technology experts, the 
individuals who care, share knowledge, keep you up to date with new technology, 
remind you to add more tests to your patch, or simply make you laugh on a 
hopeless Monday.

Thank you All!

Best Regards,
Ildikó


> Thank you for your answers! 
> 
> -Kendall Nelson
> __
> 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] [tc] [elections] Available time and top priority

2017-04-12 Thread Ildiko Vancsa

> […]
> One idea I've been considering is eliminating the one and only sacred
> one-hour weekly TC meeting, and encouraging ad-hoc discussions (on
> #openstack-dev for example) between change proposers and smaller groups
> of TC members present in the same timezone. That would give us a good
> feel of what everyone thinks, reduce noise, and happen at various times
> during the day on a public forum, giving an opportunity for more people
> to jump in the discussion. The informal nature of those discussions
> would make the governance reviews the clear focal point for coordination
> and final decision.
> 
> It's clearly not the perfect silver bullet though, so I'd very much like
> to hear other ideas :)

Sold! As far as I’m concerned. :)

As a version of this idea, I was thinking of an #openstack-tc IRC channel, but 
wanted to give it another thought before bringing it up. :) While I don’t have 
the intention to necessarily increase the number of IRC channels we have, this 
would give us the ability to follow the TC related discussion better.

By being experienced with working remotely, I like channels with smaller well 
defined scope/purpose as I can prioritize which one to read first and I don’t 
need to filter that much of the different, sometimes parallel threads to catch 
up on what happened. Also when I see activity on these channels I get a better 
indicator whether I need to/want to look into the discussion immediately and be 
part of it or not. I don’t want to decrease the importance of #openstack-dev 
(or any other already existing channel), but rather noting that it has a 
broader scope that might be distracting.

My 2 cents.

Thanks,
Ildikó


> 
> -- 
> Thierry Carrez (ttx)
> 
> __
> 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] [tc] [elections] Available time and top priority

2017-04-12 Thread Ildiko Vancsa

> On 2017. Apr 12., at 3:18, Monty Taylor  wrote:
> 
> On 04/10/2017 04:41 PM, Chris Dent wrote:
>> On Mon, 10 Apr 2017, Matt Riedemann wrote:
>> 
>>> This might also tie back in with what cdent was mentioning, and if the
>>> flurry of conversation during a TC meeting throws people off, maybe
>>> the minutes should be digested after the meeting in the mailing list.
>>> I know the meeting is logged, but it can be hard to read through that
>>> without one's eyes glazing over due to the cross-talk and locker-room
>>> towel whipping going on.
>> 
>> Aw, you beat me to it. This is part of what I was going to say in
>> response to your earlier message. I think there are at least three
>> things to do, all of which you've touched on:
>> 
>> * Alternating the meetings, despite the issues with quorum, probably
>>  ought to happen. If the issues with quorum are insurmountable that
>>  may say something important about the TC's choice to be dependent
>>  on IRC meetings. Is it habit? Doesn't most of the real voting
>>  happen in gerrit? Can more of the discussion happen in email? I
>>  think we (by we I mean all of OpenStack) can and should rely on
>>  email more than we do expressly for the purpose of enabling people
>>  to include themselves according to their own schedules and their
>>  own speeds of comprehension.
> 
> Oh god. I feel like I'm going to start a vi-vs-emacs here ...
> 
> (Before I do - I agree with alternating meetings)
> 
> Email has similar but opposite problems- in that in email the lag is often 
> too long, rather than too short. This can lead to:
> 
> - person A says a thing, then goes to sleep, because it's 1AM in their 
> timezone.
> - 1000 people start a flame war based on a poor choice of phrase in the 
> original email while person A sleeps
> - person A wakes up and is horrified to see what their simple sentence has 
> done, begins day drinking
> 
> Now, as you might imagine the specifics might vary slightly - but I say the 
> above to actually suggest that rather than it being an either/or - _both_ are 
> important, and must be balanced over time.
> 
> Email allows someone to compose an actual structured narrative, and for 
> replies to do the same. Some of us are loquatious and I imagine can be hard 
> to follow even with time to read.
> 
> IRC allows someone to respond quickly, and for someone to be like "yo, totes 
> sorry, I didn't mean that at all LOL" and to walk things back before a pile 
> of people become mortally insulted.
> 
> Like now - hopefully you'll give me a smiley in IRC ... but you might not, 
> and I'm stuck worrying that my tone came across wrong. Then if you just don't 
> respond because ZOMG-EMAIL, I might start day drinking.
> 

Big +1 on balance.

I agree in general that we need to revisit how to be more inclusive and how to 
provide as equal conditions to people all around the globe as possible.

That said I still would like to keep the ability to have allocated time for 
synchronous communication and allow the TC to be more of a team as opposed to a 
group of people driving their own and some shared missions. I think it helps 
with seeing maybe different parts but still the same big picture and making the 
group more efficient with decision making and bringing the community forward.

By being a team person I also often feel the need to discuss items as it helps 
my brain to focus and elaborate better or come up with new ideas, while with 
offline communication it is easy to get distracted and miss some aspects of the 
given problem or idea.

However, especially as a non-native-English-speaker, I sometimes like to have 
the ability to read through a discussion maybe even several times before 
forming my response to it as opposed to being rushed to answer. :)

Thanks,
Ildikó


__
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] [tc] [elections] Available time and top priority

2017-04-11 Thread Ildiko Vancsa
> 
>> Reliability is the key for them. But for the services and
>> applications that are built on top of this base? I'd like to see
>> allowing them a much more open approach: let them develop in whatever
>> language they like, release when they feel the timing is right, and
>> define their own CI testing. In other words, if you want to develop
>> in a language other than Python, go for it! If you want to use a
>> particular NoSQL database, sure thing! However, the price of that
>> freedom is that the burden will be on the project to ensure that it
>> is adequately tested, instead of laying that responsibility on our
>> infra team.
> 
> This is *precisely* what the Big Tent was all about: opening up the "what is 
> an OpenStack project" idea to more newcomers and competing implementations 
> with the condition that the shared cross-project teams like docs and infra 
> would be enablers and not doers. Instead of creating infrastructure for all 
> the new project teams, the infra team would transition to providing guidance 
> for how the project teams should set up gate jobs for themselves. Instead of 
> writing documentation for the project teams, the docs team would instead 
> provide guidance to new teams on how to write docs that integrate effectively 
> with the existing docs tooling.


I think you raised a very important point by putting emphasis on enablement. In 
my view the fact that we experienced the advantages and disadvantages of being 
more centralized in these areas is an important and useful experience. In my 
view it is crucial to remain a continuously evolving community where we are not 
afraid of making changes even if sometimes they seem to happen slowly.

Being somewhat involved in the documentation team’s activities I’m happy to say 
that the team took many steps towards and is still working on [1] the direction 
you mentioned by moving (back) content to the project repositories and by this 
making it easier for the teams to update and maintain those parts, while still 
having the guidance of the docs team both for wording and tooling.

Thanks,
Ildikó

[1] https://review.openstack.org/#/c/439122/ 
 __
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] [tc] [elections] Available time and top priority

2017-04-11 Thread Ildiko Vancsa
Hi All,

> So my question is the following: if elected, how much time do you think
> you'll be able to dedicate to Technical Committee affairs (reviewing
> proposed changes and pushing your own) ?

As a member of the OpenStack Foundation staff I have 100% of my time dedicated 
to the community let that be working with our ecosystem members, helping new 
contributors to join or keeping contact and accelerate collaboration with 
adjacent communities.

Defining an exact amount of time might be challenging as I see plenty of 
overlapping between my tasks and the TC’s scope, which means many of my 
activities serve multiple purpose. While we all have different load on a weekly 
basis I’m dedicated to secure enough time and focus on average to be a reliable 
and valuable TC member.

> If there was ONE thing, one
> initiative, one change you will actively push in the six months between
> this election round and the next, what would it be ?

As others before me pointed out very well picking one item is very hard, nearly 
impossible. I always search for the relation between items and challenges along 
with observing the different aspects of them. My main focus areas currently are 
Telecom/NFV and the Upstream Institute activities. One of the connection points 
between these two is on-boarding, which I would like to highlight here as the 
ONE.

While we’ve already come a long way with working together with the Telecom 
industry we still have a long journey ahead of us. On-boarding boils down to be 
and remain to be an open and open minded community and a helpful environment. 
In my view accepting new developers and new technologies requires very similar 
skills and mindset and requires us to keep OpenStack a welcoming and also an 
innovative place, where I would like to refer back to the challenges mentioned 
in an earlier discussion on this thread about allowing competition and 
exploring new ideas and ways of doing things.

Being or not being a TC member, my pick is to continue helping with the 
different aspects of on-boarding and make the teams along with the technical 
committee and community to be more open to accept new members with new view 
points and ideas and improve communication and collaboration between the 
related parties. In my opinion this helps to improve and maintain our solid and 
stable basis which makes us being able to deal with the technical and 
collaboration challenges - listed on this thread - together.

Thanks and Best Regards,
Ildikó


> 
> Thanks in advance for your answers !
> 
> -- 
> Thierry Carrez (ttx)
> 
> __
> 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] [election][tc] Nomination for TC

2017-04-09 Thread Ildiko Vancsa
 part in helping to further the 
efforts of providing a package that can serve the whole industry and which is 
backed up by a growing and smoothly functioning ecosystem.

Thank you for your consideration.

Best Regards,
Ildikó (ildikov)


[1] 
http://stackalytics.com/?release=all_id=ildiko-vancsa=person-day 
<http://stackalytics.com/?release=all_id=ildiko-vancsa=person-day>
[2] https://www.youtube.com/watch?v=Dvh8q5m9Ahk 
<https://www.youtube.com/watch?v=Dvh8q5m9Ahk> 
[3] https://www.opnfv.org <https://www.opnfv.org/> 
[4] https://www.opnfv.org/community/ambassadors 
<https://www.opnfv.org/community/ambassadors> 
[5] 
https://www.openstack.org/videos/paris-2014/tales-from-the-ship-navigating-the-openstack-community-seas
 
<https://www.openstack.org/videos/paris-2014/tales-from-the-ship-navigating-the-openstack-community-seas>
 
[6] 
https://www.openstack.org/videos/video/how-to-become-an-advanced-contributor 
<https://www.openstack.org/videos/video/how-to-become-an-advanced-contributor> 
[7] https://www.openstack.org/summit/austin-2016/summit-schedule/events/7510 
<https://www.openstack.org/summit/austin-2016/summit-schedule/events/7510> 

__
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] [cinder][nova] Cinder-Nova API meeting time slot change

2017-04-06 Thread Ildiko Vancsa
Hi All,

As of __today__ the Cinder-Nova API interactions meeting has a new time slot, 
__1600 UTC__.

The meeting channel is the same: __#openstack-meeting-cp__.

The patch [1] to change the slot officially is still under review with no 
conflicts.

See you soon!

Thanks and Best Regards,
Ildikó

[1] https://review.openstack.org/#/c/453199/ 
 __
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] [os-upstream-institute] Meeting reminder

2017-03-27 Thread Ildiko Vancsa
Hi,

A friendly reminder that the OpenStack Upstream Institute meeting starts in a 
bit less than an hour on #openstack-meeting-3.

See you there! :)

Thanks and Best Regards,
Ildikó
IRC: ildikov


> On 2017. Mar 20., at 21:03, Ildiko Vancsa <ildiko.van...@gmail.com> wrote:
> 
> Hi All,
> 
> Quick reminder, we have our first meeting now! :)
> 
> Thanks,
> Ildikó
> 
> 
>> On 2017. Mar 19., at 14:14, Ildiko Vancsa <ildiko.van...@gmail.com 
>> <mailto:ildiko.van...@gmail.com>> wrote:
>> 
>> Hi All,
>> 
>> Based on the results of the Doodle poll I sent out earlier the most favorite 
>> slot for the meeting is __Mondays, 2000 UTC__.
>> 
>> In order to get progress with the training preparation for Boston we will 
>> hold our first meeting on __March 20, at 2000 UTC__. The meeting channel is 
>> __#openstack-meeting-3__. You can find and extend the agenda on the meetings 
>> etherpad [2].
>> 
>> I uploaded a patch for review [1] to register the meeting slot as a 
>> permanent meeting on this channel.
>> 
>> We will look into alternatives to keep those of you involved and up to date 
>> for whom this slot is unfortunately does not work.
>> 
>> Please let me know if you have any questions or comments.
>> 
>> Thanks and Best Regards,
>> Ildikó
>> IRC: ildikov
>> 
>> 
>> [1] https://review.openstack.org/447291 <https://review.openstack.org/447291>
>> [2] https://etherpad.openstack.org/p/openstack-upstream-institute-meetings 
>> <https://etherpad.openstack.org/p/openstack-upstream-institute-meetings> 
> 

__
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] [os-upstream-institute] First meeting is starting :)

2017-03-20 Thread Ildiko Vancsa
Hi All,

Quick reminder, we have our first meeting now! :)

Thanks,
Ildikó


> On 2017. Mar 19., at 14:14, Ildiko Vancsa <ildiko.van...@gmail.com> wrote:
> 
> Hi All,
> 
> Based on the results of the Doodle poll I sent out earlier the most favorite 
> slot for the meeting is __Mondays, 2000 UTC__.
> 
> In order to get progress with the training preparation for Boston we will 
> hold our first meeting on __March 20, at 2000 UTC__. The meeting channel is 
> __#openstack-meeting-3__. You can find and extend the agenda on the meetings 
> etherpad [2].
> 
> I uploaded a patch for review [1] to register the meeting slot as a permanent 
> meeting on this channel.
> 
> We will look into alternatives to keep those of you involved and up to date 
> for whom this slot is unfortunately does not work.
> 
> Please let me know if you have any questions or comments.
> 
> Thanks and Best Regards,
> Ildikó
> IRC: ildikov
> 
> 
> [1] https://review.openstack.org/447291 <https://review.openstack.org/447291>
> [2] https://etherpad.openstack.org/p/openstack-upstream-institute-meetings 
> <https://etherpad.openstack.org/p/openstack-upstream-institute-meetings> 

__
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] [os-upstream-institute] Meeting time selected

2017-03-19 Thread Ildiko Vancsa
Hi All,

Based on the results of the Doodle poll I sent out earlier the most favorite 
slot for the meeting is __Mondays, 2000 UTC__.

In order to get progress with the training preparation for Boston we will hold 
our first meeting on __March 20, at 2000 UTC__. The meeting channel is 
__#openstack-meeting-3__. You can find and extend the agenda on the meetings 
etherpad [2].

I uploaded a patch for review [1] to register the meeting slot as a permanent 
meeting on this channel.

We will look into alternatives to keep those of you involved and up to date for 
whom this slot is unfortunately does not work.

Please let me know if you have any questions or comments.

Thanks and Best Regards,
Ildikó
IRC: ildikov


[1] https://review.openstack.org/447291 
[2] https://etherpad.openstack.org/p/openstack-upstream-institute-meetings __
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] [os-university] [os-upstream-institute] NAME CHANGE

2017-03-16 Thread Ildiko Vancsa
Hi All,

Due to some issues around the name OpenStack University we unfortunately had to 
pick a new one.

The new name of the program is OpenStack Upstream Institute.

We renamed the corresponding assets as well, so please join or move to the 
#openstack-upstream-institute IRC channel. The new ML tag is 
os-upstream-institute.

You can find the wiki page for the team and activities here: 
https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute

Sorry for the inconvenience.

Thanks and Best Regards,
Ildikó
IRC: ildikov
__
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] [os-university] Meeting time poll - ACTION needed

2017-03-15 Thread Ildiko Vancsa
Hi All,

In preparation to the upcoming OpenStack University training in Boston, on May 
6-7, we would like to start to have weekly meetings with the training team and 
those of you who would like to get involved to work on the training material 
and format.

I created a Doodle poll to see which are the most feasible time slots: 
http://doodle.com/poll/ccky8cviubdgeb9f

Please ignore the exact date and select all the slots on each day when you can 
most probably make it to the meeting! The time slots as you will see are all in 
UTC. Please keep the DST switch in mind where it hasn’t happened yet.

If you are interested please fill out the form __by the end of this week (March 
19)__.

If you have any questions please let me know.

Thanks and Best Regards,
Ildikó
IRC: ildikov
__
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] [os-university] Team updates

2017-03-15 Thread Ildiko Vancsa
Hi All,

As many of you know we are working on to create a horizontal team with liaisons 
from the project teams and volunteers from the Community overall to work on the 
upstream trainings and help with on boarding new contributors.

We named our efforts and the contribution trainings OpenStack University.

You can find further information on the following wiki page: 
https://wiki.openstack.org/wiki/OpenStack_University

Those of you who already signed up please check your details on the wiki page 
and add the missing information.

Those of you who would like to get involved please filter and use the 
[os-university] tag on the mailing list and join our IRC channel, which is 
called #openstack-university.

If you have any questions feel free to reach out to me and the team on IRC or 
here in mails. :)

Thanks and Best Regards,
Ildikó
IRC: ildikov



__
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] Upstream Training Team meeting at PTG - Are you coming?

2017-02-21 Thread Ildiko Vancsa
Hi All,

A quick reminder that we will have our face to face gathering on __Wednesday 
(tomorrow) at lunch time (12pm ET)__.

I booked Savannah 3 on the second floor (Lobby level). Please grab a lunch box 
after the morning sessions and join us for lunch if you would like to get 
involved with the Upstream Training and/or new contributor on boarding 
activities.

Thanks and Best Regards,
Ildikó
IRC: ildikov


> On 2017. Feb 15., at 13:16, Ildiko Vancsa <ildiko.van...@gmail.com> wrote:
> 
> Hi,
> 
> We are forming a virtual upstream collaboration training team including 
> everyone who’s either helping us out with maintaining and improving the 
> training material and/or who are attending the course as coaches or mentors.
> 
> We are planning to meet at the PTG in person next week on Wednesday at lunch 
> time. We picked this slot as our first face to face gathering as all of us 
> have project related assignments to drive and sessions to attend that makes 
> scheduling a meeting even more challenging.
> 
> If you are interested in what we are doing and how we are trying to make the 
> on boarding process for new contributors a pleasant experience and would like 
> to join our activities meet us there!
> 
> The meeting time is __Wednesday (February 22) lunch time__. I will share the 
> meeting point next week before the meeting.
> 
> If you would like to have a mail reminder prior to the meeting next week 
> please reach out to me.
> 
> Thanks and Best Regards,
> Ildikó
> IRC: ildikov


__
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] Upstream Training Team meeting at PTG - Are you coming?

2017-02-15 Thread Ildiko Vancsa
Hi,

We are forming a virtual upstream collaboration training team including 
everyone who’s either helping us out with maintaining and improving the 
training material and/or who are attending the course as coaches or mentors.

We are planning to meet at the PTG in person next week on Wednesday at lunch 
time. We picked this slot as our first face to face gathering as all of us have 
project related assignments to drive and sessions to attend that makes 
scheduling a meeting even more challenging.

If you are interested in what we are doing and how we are trying to make the on 
boarding process for new contributors a pleasant experience and would like to 
join our activities meet us there!

The meeting time is __Wednesday (February 22) lunch time__. I will share the 
meeting point next week before the meeting.

If you would like to have a mail reminder prior to the meeting next week please 
reach out to me.

Thanks and Best Regards,
Ildikó
IRC: ildikov
__
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] [cinder][nova] Cinder-Nova API changes meeting

2017-01-27 Thread Ildiko Vancsa
Hi All,

According to the results of our Doodle poll, the new meeting day will be 
__Thursday__ starting from next week. The time slot and the meeting channel are 
supposed to remain the same, I hope the patch [1] to register the changes gets 
merged soon to make it fully official.

In this sense, the next meeting will be __ next Thursday (February 2nd), 
1700UTC on #openstack-meeting-cp__. For topics and other information see the 
etherpad [2] for this activity.

Thanks,
Ildikó

[1] https://review.openstack.org/#/c/425414/ 
<https://review.openstack.org/#/c/425414/> 
[2] https://etherpad.openstack.org/p/cinder-nova-api-changes 
<https://etherpad.openstack.org/p/cinder-nova-api-changes> 


> On 2017. Jan 23., at 22:40, Ildiko Vancsa <ildiko.van...@gmail.com> wrote:
> 
> Hi All,
> 
> Unfortunately our current meeting slot (every Monday 1700UTC) is in collision 
> for several of the regular attendees.
> 
> In an attempt to find a new slot I checked the available meeting channels for 
> the same time slot over the week and we have at least on available currently 
> for each day. So for the first try let’s see whether we can find another day 
> during the week with the SAME (1700UTC) time slot that works better.
> 
> You can share your preference on this Doodle poll: 
> http://doodle.com/poll/9per237agrdy7rqz 
> <http://doodle.com/poll/9per237agrdy7rqz>
> 
> Thanks,
> Ildikó

__
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] Get Active in Upstream Training

2017-01-24 Thread Ildiko Vancsa
Hi All,

As most of you know we have a continuous effort to help newcomers to join our 
community by organizing and holding Upstream contribution trainings before 
every OpenStack Summit.

The training [1][2] is a 1.5 - 2 days long hands-on course focusing on the 
first steps of becoming an active OpenStack contributor. We are continuously 
working on improving and evolving the training material putting more and more 
emphasis on interactions between the participants and hands-on exercises.

The training, just like everything else in OpenStack, is community effort. The 
people who put together the material and who come to the trainings to teach, 
coach and mentor the new contributors are active members of our community.

In preparation for the Boston Summit and also the upcoming PTG in Atlanta we 
are looking for coaches and mentors to help us making the training an even 
better experience for both who hold and who attend them.

If you are interested in helping us improving the training content or resources 
that we are using and/or helping out as a mentor on any of the upcoming 
trainings please reach out to me (IRC: ildikov on Freenode, mail: 
ild...@openstack.org ) or Kendall Nelson (IRC: 
diablo_rojo on Freenode, mail: knel...@openstack.org 
) or simply reply to this mail thread and let’s 
meet on the upcoming PTG! :)

Please let us know if you have any questions or comments.

Thanks and Best Regards,
Ildikó

[1] http://docs.openstack.org/upstream-training/ 

[2] http://superuser.openstack.org/articles/openstack-upstream-training-revamp/ 
__
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] [cinder][nova] Cinder-Nova API changes meeting

2017-01-23 Thread Ildiko Vancsa
Hi All,

Unfortunately our current meeting slot (every Monday 1700UTC) is in collision 
for several of the regular attendees.

In an attempt to find a new slot I checked the available meeting channels for 
the same time slot over the week and we have at least on available currently 
for each day. So for the first try let’s see whether we can find another day 
during the week with the SAME (1700UTC) time slot that works better.

You can share your preference on this Doodle poll: 
http://doodle.com/poll/9per237agrdy7rqz 


Thanks,
Ildikó__
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] The Future of OpenStack Needs You

2016-11-28 Thread Ildiko Vancsa
Hi All,

I’m reaching out to you because we are looking for people who would like to get 
involved in the __activities around on boarding and the Upstream training__ we 
are holding before the Summits.

We had a very successful training before the Barcelona Summit [1] with around 
90 attendees during the one and a half days of the course. The training format 
orients towards a more and more __hands-on practice__ and we are looking for 
experienced people within the Community to help the new comers understand our 
processes along with the large code base we have overall and even per project.

To get you more excited I’m happy to say that our mentors had a great time with 
the students and even they learnt new things based on the feedback so far. :)

We have also started to explore a modular setup for the class which makes it 
possible to pick up only parts of it at a time in the future. This way we hope 
to __bring a subset of the modules to local events__ like OpenStack Days and 
meet-ups around the globe to reach a broader group of possible contributors.

We would like to have You on our team to support this activity and get in touch 
with possible new members of our Community to make it a good experience for 
them and for you at the same time to ensure we have people joining who 
understand our principles from day 1, successful with contributions and stay 
around after the trainings/sessions.

If you are interested in the details on how you can get involved and help with 
this activity please reach out to me (ild...@openstack.org, IRC: ildikov) or 
Kendall Nelson (knel...@openstack.org, IRC: diablo_rojo). You can also check 
the current state of the material along with our mission statement on the 
training web page [2] or join our bi-weekly (even weeks) meetings [3].

Thanks and Best Regards,
Ildikó


[1] http://superuser.openstack.org/articles/openstack-upstream-training-revamp/ 
 
[2] http://docs.openstack.org/upstream-training/ 
 
[3] http://eavesdrop.openstack.org/#Training-guides_Team_Meeting 
 

__
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] [cinder] [nova] Cinder-Nova API changes weekly meeting cancelled today

2016-10-31 Thread Ildiko Vancsa
Hi,

As many of us are either traveling or still jet lagged today we agreed to skip 
the today’s meeting.

The next meeting will be held __ next Monday (November 7) at 1700UTC__.

We had progress with the discussions last week and we seem to orient towards a 
simpler Cinder API, but we still need to discuss a few things. To be efficient 
we plan to have the next week’s meeting on Hangouts with meeting minutes on the 
IRC channel.

If you have any questions please feel free to ping me any time.

For further pointer and status information please see the links on top of this 
etherpad: https://etherpad.openstack.org/p/cinder-nova-api-changes 


Thanks and Best Regards,
Ildikó
(IRC: ildikov)__
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] [cinder][nova] API interactions meeting

2016-09-19 Thread Ildiko Vancsa
Hi All,

This is a friendly reminder that the next meeting of our series is in less than 
50 minutes, at 1700UTC on #openstack-meeting-cp.

Thanks and Best Regards,
Ildikó
__
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] [cinder] [nova] API interaction changes overview

2016-09-05 Thread Ildiko Vancsa

> On 03 Sep 2016, at 20:07, Duncan Thomas <duncan.tho...@gmail.com> wrote:
> 
> There's also another API limitation to be fixed - whether it goes in the 
> initial API fixup or gets done later, which is a round one cinder serving 
> multiple nova or other consumers: https://review.openstack.org/#/c/362637/ 
> <https://review.openstack.org/#/c/362637/>
Thanks Duncan, I added it to our etherpad to keep an eye on this one too.

> 
> On 2 September 2016 at 22:51, Matt Riedemann <mrie...@linux.vnet.ibm.com 
> <mailto:mrie...@linux.vnet.ibm.com>> wrote:
> On 9/1/2016 4:09 PM, Ildiko Vancsa wrote:
> Hi All,
> 
> 
> We had an attempt to remove ‘check_attach’ from the Nova code, as this check 
> should be purely Cinder’s responsibility. The call is partially removed [4] 
> and there’s one patch up for review to finish that work item [5]. The 
> difficulty with this one is that we have one flow that missed the 
> ‘reserve_volume’ call and therefore also the required checks on Cinder side. 
> This is corrected in the patch up for review [5], it needs some more eyes on 
> it to ensure we have the proper fix.
> 
> I haven't gone through the new experimental APIs proposed in cinder but while 
> Walter was working on [4] we realized a gap in the os-reserve call in that we 
> should pass the availability zone since nova still has to check that 
> separately:
> 
> https://github.com/openstack/nova/blob/96926a8ee182550391c30b16b410da7f598c0f39/nova/volume/cinder.py#L290
>  
> <https://github.com/openstack/nova/blob/96926a8ee182550391c30b16b410da7f598c0f39/nova/volume/cinder.py#L290>
> 
> That seems like something we could do separately early in ocata with a 
> microversion on the os-reserve API to take an optional availability_zone 
> argument and fail if it doesn't match the AZ for the volume being reserved.

@Matt: Do you mean to remove check_attach along with check_availability_zone in 
one step, when we have os-reserve properly fixed?

Thanks,
Ildikó


> 
> 
> [5] https://review.openstack.org/#/c/335358/ 
> <https://review.openstack.org/#/c/335358/>
> -- 
> 

__
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] [cinder] [nova] API interaction changes overview

2016-09-01 Thread Ildiko Vancsa
Hi All,


As we skipped a few meetings and we also reached the N-3 milestone this week I 
would like to summarise where we are currently with our plans.

At the beginning of the Newton cycle we decided to refactor the Cinder API 
around attach and detach to make Cinder more a standalone module and also to 
simplify the interaction between Nova and Cinder. The changes in high level are 
the following:

* Have one ‘create_attachment' call that will contain the functionality of the 
current ‘initialize_connection’ and ‘attach’ calls
* Have one ‘remove_attachment’ call for detach
* There are further plans to extend the Cinder API to check whether it is safe 
to remove a connection to prepare for the multi-attach use case.

The code is already on its way [1][2][3], we plan to merge the Cinder side of 
changes as an experimental API as soon as possible. We can then continue to 
test the changes on the Nova side. When the Cinder API changes are stable we 
will add proper API microversioning to enable Nova to pick it up the right way 
and use the new API with support for backward compatibility.

This work should provide the benefit of removing workarounds from the Nova code 
and make those parts more readable and easier to maintain. We will also get 
very close to support multi-attach in both modules when we progress with the 
above listed changes.

We started some work to reduce race conditions and remove a few workarounds 
from mostly the Nova code base as well during this cycle.

We had an attempt to remove ‘check_attach’ from the Nova code, as this check 
should be purely Cinder’s responsibility. The call is partially removed [4] and 
there’s one patch up for review to finish that work item [5]. The difficulty 
with this one is that we have one flow that missed the ‘reserve_volume’ call 
and therefore also the required checks on Cinder side. This is corrected in the 
patch up for review [5], it needs some more eyes on it to ensure we have the 
proper fix.

We also started to look into how to remove the unnecessary 
‘initialize_connection’ calls [6] from the Nova code. We need more review 
attention on this one also as when we will have the new calls in the Cinder API 
we need to rethink some of the current workarounds to make things like live 
migration work with the new setup.

We still have the etherpad for this work up [7], I will add the links in this 
mail to the top for better readability.

We will have the next meeting at the regular slot we use next Monday to check 
on the status and decide on what we can make happen before the Summit and also 
start to plan a little bit for the event itself as well. The meeting is on 
#openstack-meeting-cp, on Monday (Sept. 5) 1700UTC.

If you have any questions or comments please respond to this thread or join the 
meeting next Monday.


Thanks and Best Regards,
Ildikó

[1] https://review.openstack.org/#/c/327408/
[2] https://review.openstack.org/#/c/327409/
[3] https://review.openstack.org/#/c/330285/
[4] https://review.openstack.org/#/c/315789/
[5] https://review.openstack.org/#/c/335358/
[6] https://review.openstack.org/#/c/312773/
[7] https://etherpad.openstack.org/p/cinder-nova-api-changes



__
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