[openstack-dev] [Tacker] Redundancy VNFFG module in tacker

[백호성]

Dear tacker project members,

Hello. I am Hosung Baek and Ph.D.student at Korea Univ.

I am interested in the VNFFG feature in Tacker project, and I want to
develop the "Redundancy VNFFG module" in tacker.

As far as I know. it is difficult to apply the VNFFG configuration where
there is low loss requirement such as DetNet and URLLC.

Because there is no module for reliable VNFFG.

The module to be developed is described as follows.

It is a function to construct a disjoint VNFFG by adding redundancy VNFFG
module to the tacker VNFFG feature and to transmit the data to two disjoint
paths.

To implement this module, two VNFFGs must be configured for one network
service and the function to remove redundant packets in two different paths
is required.

I want to develop this module and contribute this to tacker project.

So could you tell me the contribution process in OpenStack tacker project
if possible?

Yours sincerely,

Hosung Baek.
__
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] [release] Release countdown for week R-21 and R-20, November 12-23

[Sean McGinnis]

Development Focus
-

Teams should now be focused on feature development and preparing for Berlin
Forum discussions.

General Information
---

The OpenStack Summit and Forum start on Tuesday. Hopefully many teams will have
an opportunity to work together as well as get input from folks they don't
normally get to interact with as often. This is a great opportunity to get
feedback from operators and other users to help shape the direction of the
project.

Upcoming Deadlines & Dates
--

Forum at OpenStack Summit in Berlin: November 13-15
Start using openstack-discuss ML: November 19
Stein-2 Milestone: January 10

-- 
Sean McGinnis (smcginnis)

__
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] Fw: Re: [nova] Announcing new Focal Point for s390x libvirt/kvm Nova

[zhangjing]

Thanks Andreas! also thanks Melanie's warm welcome!

It's a great honor for us to join Openstack project, hope to have more 
communications with all of you in the future, and do more contributions 
in the community!



- Original message -
From: melanie witt 
To: openstack-dev@lists.openstack.org
Cc:
Subject: Re: [openstack-dev] [nova] Announcing new Focal Point for
s390x libvirt/kvm Nova
Date: Tue, Nov 6, 2018 2:53 AM
On Fri, 2 Nov 2018 09:47:42 +0100, Andreas Scheuring wrote:
> Dear Nova Community,
> I want to announce the new focal point for Nova s390x libvirt/kvm.
>
> Please welcome "Cathy Zhang” to the Nova team. She and her team
will be responsible for maintaining the s390x libvirt/kvm
Thirdparty CI  [1] and any s390x specific code in nova and os-brick.
> I personally took a new opportunity already a few month ago but
kept maintaining the CI as good as possible. With new manpower we
can hopefully contribute more to the community again.
>
> You can reach her via
> * email: bjzhj...@linux.vnet.ibm.com
> * IRC: Cathyz
>
> Cathy, I wish you and your team all the best for this exciting
role! I also want to say thank you for the last years. It was a
great time, I learned a lot from you all, will miss it!
>
> Cheers,
>
> Andreas (irc: scheuran)
>
>
> [1] https://wiki.openstack.org/wiki/ThirdPartySystems/IBM_zKVM_CI

Thanks Andreas, for sending this note. It has been a pleasure working
with you over these years. We wish you the best of luck in your new
opportunity!

Welcome to the Nova community, Cathy! We look forward to working with
you. Please feel free to reach out to us on IRC in the #openstack-nova
channel and on this mailing list with the [nova] tag to ask questions
and share info.

Best,
-melanie





__
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] [neutron][neutron-release] feature/graphql branch rebase

[Gilles Dubreuil]

Hi Miguel,

Could you please provide permission [1] to upload commit merges?

I'm getting the following error after merging HEAD:

$ git review -R feature/graphql
remote:
remote: Processing changes: refs: 1
remote: Processing changes: refs: 1, done
To ssh://review.openstack.org:29418/openstack/neutron.git
 ! [remote rejected]   HEAD -> 
refs/publish/feature/graphql/bug/1802101 (you are not allowed to upload 
merges)
error: failed to push some refs to 
'ssh://q-1ille...@review.openstack.org:29418/openstack/neutron.git'


Thanks,
Gilles

[1] 
https://github.com/openstack-infra/gerrit/blob/master/Documentation/error-not-allowed-to-upload-merges.txt



On 23/10/18 7:30 pm, Gilles Dubreuil wrote:


Hi Miguel,

Thank you for your help.

I'll use those precious instructions next time.

Cheers,
Gilles

On 16/10/18 1:32 am, Miguel Lavalle wrote:

Hi Gilles,

The merge of master into feature/graphql  has been approved: 
https://review.openstack.org/#/c/609455. In the future, you can 
create your own merge patch following the instructions here: 
https://docs.openstack.org/infra/manual/drivers.html#merge-master-into-feature-branch. 
The Neutron team will catch it in Gerrit and review it


Regards

Miguel

On Thu, Oct 4, 2018 at 11:44 PM Gilles Dubreuil > wrote:


Hey Neutron folks,

I'm just reiterating the request.

Thanks


On 20/06/18 11:34, Gilles Dubreuil wrote:
> Could someone from the Neutron release group rebase
feature/graphql
> branch against master/HEAD branch please?
>
> Regards,
> Gilles
>
>


--
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email:gil...@redhat.com
GitHub/IRC: gildub
Mobile: +61 400 894 219


--
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email: gil...@redhat.com
GitHub/IRC: gildub
Mobile: +61 400 894 219

__
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] [openstack-operators] [qa] [berlin] QA Team & related sessions at berlin summit

[Ghanshyam Mann]

Hello everyone,

Along with project updates & onboarding sessions, QA team will host QA feedback 
sessions in berlin summit.  Feel free to catch us next week for any QA related 
questions or if you need help to contribute in QA (we are really looking 
forward to onbaord new contributor in QA). 

Below are the QA related sessions, feel free to append the list if i missed 
anything. I am working on onboarding/forum sessions etherpad and will send the 
link tomorrow. 

Tuesday:
  1. OpenStack QA - Project Update.   [1]
  2. OpenStack QA - Project Onboarding.   [2]
  3. OpenStack Patrole – Foolproofing your OpenStack Deployment [3]

Wednesday:
  4. Forum: Users / Operators adoption of QA tools / plugins.  [4]

Thursday:
  5. Using Rally/Tempest for change validation (OPS session) [5]

[1] 
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22763/openstack-qa-project-update
 
[2] 
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22762/openstack-qa-project-onboarding
[3] 
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22148/openstack-patrole-foolproofing-your-openstack-deployment
[4] 
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22788/users-operators-adoption-of-qa-tools-plugins
 
[5] 
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22837/using-rallytempest-for-change-validation-ops-session
 

-gmann


__
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] [senlin] Meeting today at 530 UTC

[Duc Truong]

Everyone,

As a reminder, we will be having our regular meeting today at 530 UTC.

The meetings for Nov 16 and Nov 23 will be cancelled due to the summit
next week and the U.S. Thanksgiving holiday the following week,

Duc

__
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] [manila] [contribute]

[Goutham Pacha Ravi]

On Thu, Nov 8, 2018 at 6:07 AM Sofia Enriquez  wrote:

> Hi Leni, welcome!
>
> 1) Devstack[1] plays a *main *role in the development workflow.
> It's an easier way to get a full environment to work in Manila, we use it
> every day. I recommend you to use it in a VM.
> You can find many tutorials about how to use Devstack, I just let you one
> [2]
>
> 2) I can't find *low-hanging-fruit* bugs in Manila. However,
> good-first-bugs are tagged as *low-hanging-fruit *for example, cinder's[3]
>
> Today at *15:00 UTC *It's  Weekly Manila Team Meeting at IRC (channel
> #openstack-meeting-alt) on Freenode.
>
>
Thank you so much for looking Sofia, and thanks for reaching out Leni! I
just reported a low-hanging-fruit bug in manila

https://bugs.launchpad.net/manila/+bugs?field.tag=low-hanging-fruit

I've added some steps to get you started to land a bug fix on the bug
report. Please feel free to join #openstack-manila on IRC (
https://docs.openstack.org/infra/manual/irc.html) and reach out in case
you're stuck.

I'd also encourage you to look at low-hanging-fruit in the
python-manilaclient and manila-ui projects as well:

https://bugs.launchpad.net/python-manilaclient/+bugs?field.tag=low-hanging-fruit
https://bugs.launchpad.net/manila-ui/+bugs?field.tag=low-hanging-fruit

Happy coding,
Goutham (gouthamr)


> Have fun!
> Sofia
> irc: enriquetaso
> [1]
> https://docs.openstack.org/zun/latest/contributor/quickstart.html#exercising-the-services-using-devstack
> [2]
> https://enriquetaso.wordpress.com/2016/05/07/installing-devstack-on-a-vagrant-virtual-machine/
> [3] https://bugs.launchpad.net/cinder/+bugs?field.tag=low-hanging-fruit
>
> On Thu, Nov 8, 2018 at 7:41 AM Leni Kadali Mutungi 
> wrote:
>
>> Hi Tom
>>
>> Thanks for the warm welcome. I've gone through the material and I would
>> like to understand a few things:
>>
>> 1. What's the role of devstack in the development workflow?
>> 2. Where can I find good-first-bugs? A bug that is simple to do
>> (relatively ;)) and allows me to practice what I've read up on in
>> Developer's Guide. I looked through the manila bugs on Launchpad but I
>> didn't see anything marked easy or good-first-bug or its equivalent for
>> manila. I am a bit unfamiliar with Launchpad so that may have played a
>> role :).
>>
>> Your guidance is appreciated.
>>
>> On 10/19/18 5:55 PM, Tom Barron wrote:
>> > On 19/10/18 15:27 +0300, Leni Kadali Mutungi wrote:
>> >> Hi all.
>> >>
>> >> I've downloaded the manila project from GitHub as a zip file, unpacked
>> >> it and have run `git fetch --depth=1` and been progressively running
>> >> `git fetch --deepen=5` to get the commit history I need. For future
>> >> reference, would a shallow clone e.g. `git clone depth=1` be enough to
>> >> start working on the project or should one have the full commit
>> >> history of the project?
>> >>
>> >> --
>> >> -- Kind regards,
>> >> Leni Kadali Mutungi
>> >
>> > Hi Leni,
>> >
>> > First I'd like to extend a warm welcome to you as a new manila project
>> > contributor!  We have some contributor/developer documentation [1] that
>> > you may find useful. If you find any gaps or misinformation, we will be
>> > happy to work with you to address these.  In addition to this email
>> > list, the #openstack-manila IRC channel on freenode is a good place to
>> > ask questions.  Many of us run irc bouncers so we'll see the question
>> > even if we're not looking right when it is asked.  Finally, we have a
>> > meeting most weeks on Thursdays at 1500UTC in #openstack-meeting-alt --
>> > agendas are posted here [2].  Also, here is our work-plan for the
>> > current Stein development cycle [3].
>> >
>> > Now for your question about shallow clones.  I hope others who know
>> more
>> > will chime in but here are my thoughts ...
>> >
>> > Although having the full commit history for the project is useful, it
>> is
>> > certainly possible to get started with a shallow clone of the project.
>> > That said, I'm not sure if the space and download-time/bandwidth gains
>> > are going to be that significant because once you have the workspace
>> you
>> > will want to run unit tests, pep8, etc. using tox as explained in the
>> > developer documentation mentioned earlier.   That will download virtual
>> > environments for manila's dependencies in your workspace (under .tox
>> > directory) that dwarf the space used for manila proper.
>> >
>> > $ git clone --depth=1 g...@github.com:openstack/manila.git
>> shallow-manila
>> > Cloning into 'shallow-manila'...
>> > ...
>> > $ git clone g...@github.com:openstack/manila.git deep-manila
>> > Cloning into 'deep-manila'...
>> > ...
>> > $ du -sh shallow-manila deep-manila/
>> > 20Mshallow-manila
>> > 35Mdeep-manila/
>> >
>> > But after we run tox inside shallow-manila and deep-manila we see:
>> >
>> > $ du -sh shallow-manila deep-manila/
>> > 589Mshallow-manila
>> > 603Mdeep-manila/
>> >
>> > Similarly, you are likely to want to run devstack locally and that will
>> > clone the repos

Re: [openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration

[Duc Truong]

Thanks for getting the forum setup.

I have added some high-level autoscaling use case to the etherpad that will
help during the discussion.

Duc (dtruong)

On Wed, Oct 24, 2018 at 2:10 AM Rico Lin  wrote:

> Hi all, I'm glad to notify you all that our forum session has been
> accepted [1] and that forum time schedule (Thursday, November 15,
> 9:50am-10:30am) should be stable by now. So please save your schedule for
> it!!
> Any feedback are welcome!
>
>
>
> [1]
> https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22753/autoscaling-integration-improvement-and-feedback
>
> On Tue, Oct 9, 2018 at 3:07 PM Rico Lin  wrote:
>
>> a reminder for all, please put your ideas/thoughts/suggest actions in our
>> etherpad [1],
>> which we gonna use for further discussion in Forum, or in PTG if we got
>> no forum for it.
>> So we won't be missing anything.
>>
>>
>>
>> [1] https://etherpad.openstack.org/p/autoscaling-integration-and-feedback
>>
>> On Tue, Oct 9, 2018 at 2:22 PM Qiming Teng  wrote:
>>
>>> > >One approach would be to switch the underlying Heat AutoScalingGroup
>>> > >implementation to use Senlin and then deprecate the AutoScalingGroup
>>> > >resource type in favor of the Senlin resource type over several
>>> > >cycles.
>>> >
>>> > The hard part (or one hard part, at least) of that is migrating the
>>> existing
>>> > data.
>>>
>>> Agreed. In an ideal world, we can transparently transplant the "scaling
>>> group" resource implementation onto something (e.g. a library or an
>>> interface). This sounds like an option for both teams to brainstorm
>>> together.
>>>
>>> - Qiming
>>>
>>>
>>>
>>> __
>>> 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
>>>
>>
>>
>> --
>> May The Force of OpenStack Be With You,
>>
>> *Rico Lin*irc: ricolin
>>
>>
>
> --
> May The Force of OpenStack Be With You,
>
> *Rico Lin*irc: ricolin
>
> __
> 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] networking-vpp 18.10 for VPP 18.10 is now available

[Naveen Joy (najoy)]

Hello All,

In conjunction with the release of VPP 18.10, we'd like to invite you all to 
try out networking-vpp 18.10 for VPP 18.10.
As many of you may already know, VPP is a fast user space forwarder based on 
the DPDK toolkit. VPP uses vector packet
processing algorithms to minimize the CPU time spent on each packet to maximize 
throughput.

Networking-vpp is a ML2 mechanism driver that controls VPP on your control and 
compute hosts to provide fast L2 forwarding
under Neutron.

In this release, we have made improvements to fully support the network trunk 
service plugin. Using this plugin, you can attach
multiple networks to an instance by binding it to a single vhostuser trunk 
port. The APIs are the same as the OpenStack Neutron trunk
service APIs. You can also now bind and unbind subports to a bound network 
trunk.

Another feature we have improved in this release is the Tap-as-a-service(TaaS). 
The TaaS code has been updated to handle any out of order
etcd messages received during agent restarts. You can use this service to 
create remote port mirroring capability for tenant virtual networks.

Besides the above, this release also has several bug fixes, VPP 18.10 API 
compatibility and stability related improvements.

The README [1] explains how you can try out VPP using devstack: the devstack 
plugin will deploy the mechanism driver and VPP 18.10
and should give you a working system with a minimum of hassle.

We will be continuing our development between now and VPP's 19.01 release. 
There are several features we're planning to work on
and we will keep you updated through our bugs list [2]. We welcome anyone who 
would like to come help us.

Everyone is welcome to join our biweekly IRC meetings, every other Monday (the 
next one is due this Monday at 0800 PT = 1600 GMT.
--
Ian & Naveen

[1]https://github.com/openstack/networking-vpp/blob/master/README.rst
[2]http://goo.gl/i3TzAt
__
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] [nova] no meeting the next two weeks

[melanie witt]

Howdy all,

This is a heads up that we will not hold a nova meeting next week 
November 15 because of summit week. And we will also not hold a nova 
meeting the following week November 22 because of the US holiday of 
Thanksgiving, as we're unlikely to find anyone to run it during the 2100 
UTC time slot.


Meetings will resume on November 29 at 1400 UTC.

I'm looking forward to seeing all of you at the summit next week!

Cheers,
-melanie

__
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] OpenDev, the future of OpenStack Infra

[Clark Boylan]

Hello everyone,

Sorry for another cross post so soon.

In the land before time we had Stackforge. 

Stackforge gave non-OpenStack projects a place to live with their own clearly 
defined "not OpenStack" namespacing. As the wheel of time spun we realized that 
many Stackforge projects were becoming OpenStack projects and we would have to 
migrate them. This involved Gerrit downtimes to rename things safely. To ease 
the pain of this, the TC decided that all projects developed in the OpenStack 
Infrastructure could live under the OpenStack git namespace to simplify 
migrations.

Unfortunately this had the effect of creating confusion over which projects 
were officially a part of OpenStack, and whether or not projects that were not 
OpenStack could use our project hosting. Stackforge lived on under a different 
name, "unofficial project hosting", but many potential infrastructure users 
either didn't understand this or didn't want that strong association to 
OpenStack for their project hosting [0].

Turns out that we want to be able to host OpenStack and non-OpenStack projects 
together without confusion in a way that makes all of the projects involved 
happy. In an effort to make this a reality the OpenStack Infra team has been 
working through a process to rename itself to make it clear that our awesome 
project infrastructure and open collaboration tooling is community run, not 
just for OpenStack, but for others that want to be involved. To this end we've 
acquired the opendev.org domain which will allow us to host services under a 
neutral name as the OpenDev Infrastructure team.

The OpenStack community will continue to be the largest and a primary user for 
the OpenDev Infrastructure team, but our hope in making our infrastructure 
services more inclusive is that we'll also attract new contributors, which will 
ultimately benefit OpenStack and other open infrastructure projects.

Our goals for OpenDev are to:
  * Encourage additional active infrastructure contributors to help us scale. 
Make it clear that this is community-run tooling & infrastructure and everyone 
can get involved.
  * Make open source collaboration tools and project infrastructure more 
accessible to those that want it.
  * Have exposure to and dogfooding of OpenStack clouds as viable open source 
cloud providers.
  * Enable more projects to take advantage of the OpenStack-pioneered model of 
development and collaboration, including recommended practices like code review 
and gating.
  * Help build relationships with new and adjacent open source projects and 
create an inclusive space for collaboration and open source development.

Much of this is still in the early planning stages. This is the infrastructure 
team's current thinking on the subject, but understand we have an existing 
community from which we'd like to see buy-in and involvement. To that end we 
have tried to compile a list of expected FAQ/Q&A information below, but feel 
free to followup either on this thread or with myself for anything we haven't 
considered already.

Any transition will be slow and considered so don't expect everything to change 
overnight. But don't be surprised if you run into some new HTTP redirects as we 
reorganize the names under which services run. We'll also be sure to keep you 
informed on any major (and probably minor) transition steps so that they won't 
surprise you.

Thank you,
Clark

[0] It should be noted that some projects did not mind this and hosted with 
OpenStack Infra anyway. ARA is an excellent example of this.

FAQ

* What is OpenDev?
OpenDev is community-run tools and infrastructure services for collaboratively 
developing open source software. 

The OpenDev infrastruture team is the community of people who operate the 
infrastructure under the umbrella of the OpenStack Foundation.

* What services are you offering? What is the expected timeline?
In the near-term we expect to transition simple services like etherpad hosting 
to the OpenDev domain. It wil take us months and potentially up to a year to 
transition key infrastructure pieces like Git and Gerrit.

Example services managed by the team today include etherpad, wiki, the zuul and 
nodepool CI system, git and gerrit, and other minor systems like pbx 
conferencing and survey tools.

* Where will these services live?
We've acquired opendev.org and are planning to set up DNS hosting very soon. We 
will post a simple information page and FAQ on the website and build it out as 
necessary over time. 

* Why are you changing from the OpenStack infrastructure team to the OpenDev 
infrastructure team?
In the same way we want to signal that our services are not strictly for 
OpenStack projects, and that not every project using our services is an 
official part of OpenStack, we want to make it clear that our team also serves 
this larger community.

* Who should use OpenDev services? Does it have to be projects related to 
OpenStack, or any open source projects?
In short, open

Re: [openstack-dev] [oslo] Next two meetings

[Ben Nemec]

On 11/7/18 2:19 PM, Ben Nemec wrote:

Hi,

Next week is summit and a lot of our contributors will be traveling 
there on Monday, so let's skip the meeting. The following week I will 
also be out, so if anyone wants to run the meeting please let me know. 
Otherwise we'll skip that one too and reconvene after Thanksgiving.


If you need your Oslo fix for next week, come see us in Berlin: 
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22952/oslo-project-onboarding 



(I just noticed that is listed as a project onboarding - it's actually a 
project update. I'll look into getting that fixed)


This is fixed, so you can now find the session at 
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22952/oslo-project-update


__
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] [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for Contributions - Deadline Approaching

[Bogdan Dobrelya]

Hi folks.
The deadline for papers seems to be extended till Nov 17, so that's a 
great news!

I finished drafting the position paper [0],[1].

Please /proof read and review. There is also open questions placed there 
and it would be really nice to have a co-author here for any of those 
items remaining...


I'm also looking for some help with... **uploading PDF** to EDAS system! 
:) It throws on me:
 pdf	notstampable	The PDF file is not compliant with PDF standards and 
cannot be stamped (see FAQ)...


And FAQ says:


"First, try using the most current version of dvipdf for LaTeX or the most 
current version of Word. You can also distill the file by using Acrobat (Pro, not 
Acrobat Reader):
* Open the PDF file in Acrobat Pro;
* Go to the File Menu > Save As or File > Export To... (in Adobe DC Pro) or File > 
Save As Other... > More Options > Postscript (in Adobe Pro version 11)
* Give the file a new name (do not overwrite the original file);
* Under "Save As Type", choose "PostScript File (*.ps)"
* Open Distiller and browse for this file or go to the directory where the file 
exists and double click on the file - this will open and run Distiller and 
regenerate the PDF file.

If you do not have Acrobat Pro, you can also try to save the PostScript version via Apple Preview, using the 
"Print..." menu and the "PDF v" selector in the lower left hand corner to pick "Save as 
PostScript...". Unfortunately, Apple Preview saves PDF files as version 1.3, which is not acceptable to PDF 
Xpress, but tools such as docupub appear to produce compliant PDF."



I have yet tried those MS word/adobe pro and distutils dances ( I think 
I should try that as well... ), but neither docupub [2] nor dvipdf(m) 
for LaTeX helped to produce a pdf edas can eat :-(


[0] 
https://github.com/bogdando/papers-ieee/blob/master/ICFC-2019/LaTeX/position_paper_1570506394.pdf
[1] 
https://github.com/bogdando/papers-ieee/blob/master/ICFC-2019/LaTeX/position_paper_1570506394.tex

[2] https://docupub.com/pdfconvert/


Folks, I have drafted a few more sections [0] for your /proof reading 
and kind review please. Also left some notes for TBD things, either for 
the potential co-authors' attention or myself :)


[0] 
https://github.com/bogdando/papers-ieee/blob/master/ICFC-2019/LaTeX/position_paper_1570506394.pdf



--
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
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] [nova] about resize the instance

[Chris Friesen]

On 11/8/2018 5:30 AM, Rambo wrote:


  When I resize the instance, the compute node report that 
"libvirtError: internal error: qemu unexpectedly closed the monitor: 
2018-11-08T09:42:04.695681Z qemu-kvm: cannot set up guest memory 
'pc.ram': Cannot allocate memory".Has anyone seen this situation?And 
the ram_allocation_ratio is set 3 in nova.conf.The total memory is 
125G.When I use the "nova hypervisor-show server" command to show the 
compute node's free_ram_mb is -45G.If it is the result of excessive use 
of memory?

Can you give me some suggestions about this?Thank you very much.


I suspect that you simply don't have any available memory on that system.

What is your kernel overcommit setting on the host?  If 
/proc/sys/vm/overcommit_memory is set to 2, then try either changing the 
overcommit ratio or setting it to 1 to see if that makes a difference.


Chris

__
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] Diversity and Inclusion at OpenStack Summit

[Amy Marrich]

Forgot one important one on Wednesday, 12:30 - 1:40!!!

We are very pleased to have the very first *Diversity Networking Lunch*
which os being sponsored by Intel[0]. In the past there was feedback that
allies and others didn't wish to intrude on the WoO lunch and Intel was all
for this change to a more open Diversity lunch! So please come and join us
on Wednesday for lunch!!

See you all soon,

Amy Marrich (spotz)
Diversity and Inclusion WG Chair


[0] -
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22850/diversity-networking-lunch-sponsored-by-intel



On Wed, Nov 7, 2018 at 9:18 AM, Amy Marrich  wrote:

> I just wanted to pass on a few things we have going on during Summit that
> might be of interest!
>
> *Diversity and Inclusion GroupMe* - Is it your first summit and you don't
> know anyone else? Maybe you just don't want to travel to and from the venue
> alone? In the tradition of WoO, I have created a GroupMe so people can
> communicate with each other. If you would like to be added to the group
> please let me know and I'll get you added!
>
> *Night Watch Tour *- On Wednesday night at 10PM, members of the community
> will be meeting up to go on a private Night Watch Tour[0]! This is a
> non-alcoholic activity for those wanting to get with other Stackers, but
> don't want to partake in the Pub Crawl! We've been doing these since Boston
> and they're a lot of fun. The cost is 15 euros cash and I do need you to
> RSVP to me as we will need to get a second guide if we grow too large!
>
> Summit sessions you may wish to attend:
> Tuesday -
> *Speed Mentoring Lunch* [1] 12:30 -1:40 - We are still looking for both
> Mentors and Mentees for the session so please RSVP! This is another great
> way to meet people in the community, learn more and give back!!!
> *Cohort Mentoring BoF* [2] 4:20 - 5:00 - Come talk to the people in
> charge of the Cohort Mentoring program and see how you can get involved as
> a Mentor or Mentee!
> *D&I WG Update* [3] 5:10- 5:50 - Learn what we've been up to, how you can
> get involved, and what's next.
>
> Wednesday -
> *Git and Gerrit Hands-On Workshop* [4] 3:20 - 4:20 - So you've seen some
> exciting stuff this week but don't know how to get setup to start
> contributing? This session is for you in that we'll walk you through
> getting your logins, your system configured and if time allows even how to
> submit a bug and patch!
>
> Thursday -
> *Mentoring Program Reboot* [5] 3:20 - 4:00 - Learn about the importance
> of mentoring, the changes in the OPenStack mentoring programs and how you
> can get involved.
>
> Hope to see everyone in Berlin next week! Please feel free to contact me
> or grab me in the hall next week with any questions or to join in the fun!
>
> Amy Marrich (spotz)
> Diversity and Inclusion WG Chair
>
> [0] - http://baerentouren.de/nachtwache_en.html
> [1] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/22873/speed-mentoring-lunch
> [2] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/22892/long-term-mentoring-keeping-the-party-going
> [3] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/22893/diversity-and-inclusion-wg-update
> [4] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/21943/git-and-gerrit-hands-on-workshop
> [5] - https://www.openstack.org/summit/berlin-2018/summit-
> schedule/events/22443/mentoring-program-reboot
>
__
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][all] TC office hours is started now on #openstack-tc

[Ghanshyam Mann]

Hi All, 

TC office hour is started on #openstack-tc channel. Feel free to reach to us 
for anything you want discuss/input/feedback/help from TC. 

- TC 





__
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] [manila] [contribute]

[Sofia Enriquez]

Hi Leni, welcome!

1) Devstack[1] plays a *main *role in the development workflow.
It's an easier way to get a full environment to work in Manila, we use it
every day. I recommend you to use it in a VM.
You can find many tutorials about how to use Devstack, I just let you one
[2]

2) I can't find *low-hanging-fruit* bugs in Manila. However,
good-first-bugs are tagged as *low-hanging-fruit *for example, cinder's[3]

Today at *15:00 UTC *It's  Weekly Manila Team Meeting at IRC (channel
#openstack-meeting-alt) on Freenode.

Have fun!
Sofia
irc: enriquetaso
[1]
https://docs.openstack.org/zun/latest/contributor/quickstart.html#exercising-the-services-using-devstack
[2]
https://enriquetaso.wordpress.com/2016/05/07/installing-devstack-on-a-vagrant-virtual-machine/
[3] https://bugs.launchpad.net/cinder/+bugs?field.tag=low-hanging-fruit

On Thu, Nov 8, 2018 at 7:41 AM Leni Kadali Mutungi 
wrote:

> Hi Tom
>
> Thanks for the warm welcome. I've gone through the material and I would
> like to understand a few things:
>
> 1. What's the role of devstack in the development workflow?
> 2. Where can I find good-first-bugs? A bug that is simple to do
> (relatively ;)) and allows me to practice what I've read up on in
> Developer's Guide. I looked through the manila bugs on Launchpad but I
> didn't see anything marked easy or good-first-bug or its equivalent for
> manila. I am a bit unfamiliar with Launchpad so that may have played a
> role :).
>
> Your guidance is appreciated.
>
> On 10/19/18 5:55 PM, Tom Barron wrote:
> > On 19/10/18 15:27 +0300, Leni Kadali Mutungi wrote:
> >> Hi all.
> >>
> >> I've downloaded the manila project from GitHub as a zip file, unpacked
> >> it and have run `git fetch --depth=1` and been progressively running
> >> `git fetch --deepen=5` to get the commit history I need. For future
> >> reference, would a shallow clone e.g. `git clone depth=1` be enough to
> >> start working on the project or should one have the full commit
> >> history of the project?
> >>
> >> --
> >> -- Kind regards,
> >> Leni Kadali Mutungi
> >
> > Hi Leni,
> >
> > First I'd like to extend a warm welcome to you as a new manila project
> > contributor!  We have some contributor/developer documentation [1] that
> > you may find useful. If you find any gaps or misinformation, we will be
> > happy to work with you to address these.  In addition to this email
> > list, the #openstack-manila IRC channel on freenode is a good place to
> > ask questions.  Many of us run irc bouncers so we'll see the question
> > even if we're not looking right when it is asked.  Finally, we have a
> > meeting most weeks on Thursdays at 1500UTC in #openstack-meeting-alt --
> > agendas are posted here [2].  Also, here is our work-plan for the
> > current Stein development cycle [3].
> >
> > Now for your question about shallow clones.  I hope others who know more
> > will chime in but here are my thoughts ...
> >
> > Although having the full commit history for the project is useful, it is
> > certainly possible to get started with a shallow clone of the project.
> > That said, I'm not sure if the space and download-time/bandwidth gains
> > are going to be that significant because once you have the workspace you
> > will want to run unit tests, pep8, etc. using tox as explained in the
> > developer documentation mentioned earlier.   That will download virtual
> > environments for manila's dependencies in your workspace (under .tox
> > directory) that dwarf the space used for manila proper.
> >
> > $ git clone --depth=1 g...@github.com:openstack/manila.git shallow-manila
> > Cloning into 'shallow-manila'...
> > ...
> > $ git clone g...@github.com:openstack/manila.git deep-manila
> > Cloning into 'deep-manila'...
> > ...
> > $ du -sh shallow-manila deep-manila/
> > 20Mshallow-manila
> > 35Mdeep-manila/
> >
> > But after we run tox inside shallow-manila and deep-manila we see:
> >
> > $ du -sh shallow-manila deep-manila/
> > 589Mshallow-manila
> > 603Mdeep-manila/
> >
> > Similarly, you are likely to want to run devstack locally and that will
> > clone the repositories for the other openstack components you need and
> > the savings from shallow clones won't be that significant relative to
> > the total needed.
> >
> > Happy developing!
> >
> > -- Tom Barron (Manila PTL) irc: tbarron
> >
> > [1] https://docs.openstack.org/manila/rocky/contributor/index.html
> > [2] https://wiki.openstack.org/wiki/Manila/Meetings
> > [3] https://wiki.openstack.org/wiki/Manila/SteinCycle
> >
> >
> __
> > 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
>
> --
> -- Kind regards,
> Leni Kadali Mutungi
>
> __
> OpenStack Development Mailing List (not for usage q

[openstack-dev] [sahara] No meeting today

[Telles Nobrega]

Sorry for the late notice but we are not having sahara meeting today.

Thanks folks,
-- 

TELLES NOBREGA

SOFTWARE ENGINEER

Red Hat Brasil  

Av. Brg. Faria Lima, 3900 - 8º andar - Itaim Bibi, São Paulo

tenob...@redhat.com

TRIED. TESTED. TRUSTED. 
 Red Hat é reconhecida entre as melhores empresas para trabalhar no Brasil
pelo Great Place to Work.
__
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] [vitrage] I have some problems with Prometheus alarms in vitrage.

[Ifat Afek]

Hi,

We solved the timestamp bug. There are two patches for master [1] and
stable/rocky [2].
I'll check the other issues next week.

Regards,
Ifat

[1] https://review.openstack.org/#/c/616468/
[2] https://review.openstack.org/#/c/616469/


On Wed, Oct 31, 2018 at 10:59 AM Won  wrote:

>
 [image: image.png]
 The time stamp is recorded well in log(vitrage-graph,collect etc), but
 in vitrage-dashboard it is marked 2001-01-01.
 However, it seems that the time stamp is recognized well internally
 because the alarm can be resolved and is recorded well in log.

>>>
__
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] [nova] about resize the instance

[Rambo]

When I resize the instance, the compute node report that "libvirtError: 
internal error: qemu unexpectedly closed the monitor: 
2018-11-08T09:42:04.695681Z qemu-kvm: cannot set up guest memory 'pc.ram': 
Cannot allocate memory".Has anyone seen this situation?And the 
ram_allocation_ratio is set 3 in nova.conf.The total memory is 125G.When I use 
the "nova hypervisor-show server" command to show the compute node's 
free_ram_mb is -45G.If it is the result of excessive use of memory?
Can you give me some suggestions about this?Thank you very much.
-- Original --
From:  "Rambo";
Date:  Thu, Nov 8, 2018 05:45 PM
To:  "OpenStack Developmen"; 

Subject:  [openstack-dev]  [nova] about resize the instance

 
Hi,all

When we resize/migrate instance, if error occurs on source compute 
node, the instance state can rollback to active currently.But if error occurs 
in "finish_resize" function on destination compute node, the instance state 
would not rollback to active. Is there a bug, or if anyone plans to change 
this?Can you tell me more about this ?Thank you very much.




















Best Regards
Rambo__
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] [manila] [contribute]

[Leni Kadali Mutungi]

Hi Tom

Thanks for the warm welcome. I've gone through the material and I would 
like to understand a few things:


1. What's the role of devstack in the development workflow?
2. Where can I find good-first-bugs? A bug that is simple to do 
(relatively ;)) and allows me to practice what I've read up on in 
Developer's Guide. I looked through the manila bugs on Launchpad but I 
didn't see anything marked easy or good-first-bug or its equivalent for 
manila. I am a bit unfamiliar with Launchpad so that may have played a 
role :).


Your guidance is appreciated.

On 10/19/18 5:55 PM, Tom Barron wrote:

On 19/10/18 15:27 +0300, Leni Kadali Mutungi wrote:

Hi all.

I've downloaded the manila project from GitHub as a zip file, unpacked 
it and have run `git fetch --depth=1` and been progressively running 
`git fetch --deepen=5` to get the commit history I need. For future 
reference, would a shallow clone e.g. `git clone depth=1` be enough to 
start working on the project or should one have the full commit 
history of the project?


--
-- Kind regards,
Leni Kadali Mutungi


Hi Leni,

First I'd like to extend a warm welcome to you as a new manila project 
contributor!  We have some contributor/developer documentation [1] that 
you may find useful. If you find any gaps or misinformation, we will be 
happy to work with you to address these.  In addition to this email 
list, the #openstack-manila IRC channel on freenode is a good place to 
ask questions.  Many of us run irc bouncers so we'll see the question 
even if we're not looking right when it is asked.  Finally, we have a 
meeting most weeks on Thursdays at 1500UTC in #openstack-meeting-alt -- 
agendas are posted here [2].  Also, here is our work-plan for the 
current Stein development cycle [3].


Now for your question about shallow clones.  I hope others who know more 
will chime in but here are my thoughts ...


Although having the full commit history for the project is useful, it is 
certainly possible to get started with a shallow clone of the project.  
That said, I'm not sure if the space and download-time/bandwidth gains 
are going to be that significant because once you have the workspace you 
will want to run unit tests, pep8, etc. using tox as explained in the 
developer documentation mentioned earlier.   That will download virtual 
environments for manila's dependencies in your workspace (under .tox 
directory) that dwarf the space used for manila proper.


$ git clone --depth=1 g...@github.com:openstack/manila.git shallow-manila
Cloning into 'shallow-manila'...
...
$ git clone g...@github.com:openstack/manila.git deep-manila
Cloning into 'deep-manila'...
...
$ du -sh shallow-manila deep-manila/
20M    shallow-manila
35M    deep-manila/

But after we run tox inside shallow-manila and deep-manila we see:

$ du -sh shallow-manila deep-manila/
589M    shallow-manila
603M    deep-manila/

Similarly, you are likely to want to run devstack locally and that will 
clone the repositories for the other openstack components you need and 
the savings from shallow clones won't be that significant relative to 
the total needed.


Happy developing!

-- Tom Barron (Manila PTL) irc: tbarron

[1] https://docs.openstack.org/manila/rocky/contributor/index.html
[2] https://wiki.openstack.org/wiki/Manila/Meetings
[3] https://wiki.openstack.org/wiki/Manila/SteinCycle

__
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


--
-- Kind regards,
Leni Kadali Mutungi

__
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] [nova] about resize the instance

[Rambo]

Hi,all

When we resize/migrate instance, if error occurs on source compute 
node, the instance state can rollback to active currently.But if error occurs 
in "finish_resize" function on destination compute node, the instance state 
would not rollback to active. Is there a bug, or if anyone plans to change 
this?Can you tell me more about this ?Thank you very much.




















Best Regards
Rambo__
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] [Searchlight] Team meeting cancelled today

[Trinh Nguyen]

Hi team,

There're not many things have been done last week so we will cancel the
team meeting today. Just a reminder that we now focus on developing the use
cases for the Stein-2 milestone.

See you in the next two weeks.

Bests,

-- 
*Trinh Nguyen*
*www.edlab.xyz *
__
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