Hi forks,
I’m beginner about Openstack developments. I’ve been really interested in
to know about Openstack and wanted to modify and test it.
But I’m using PyCharm in the Windows 7 but, It’s very hard to programming
and testing when I tried to change code little bit.
I hope you guys are
Djimeli Konrad wrote:
My name is Djimeli Konrad a second year computer science student from
the University of Buea Cameroon, Africa. I am GSoC 2015 participant,
and I have also worked on some open-source projects on github
(http://github.com/djkonro) and sourceforge
(https://sourceforge.net/u/ko
Shinobu Kinjo wrote:
I guess, it's usable. [1] [2] [3], probably and more...
The reason why still I can just guess is that there is a bunch of
documentations!!
It's one of great works but too much.
We have transitioned most of the documentation off the wiki, but there
are still a number of pa
Hi,
This is a matter of personal preference, most people use lightweight editors
like for example:
Visual Studio Code, Sublime Text, Notepad++, Atom or even vim.
Others prefer a full IDE with integrated debugger, like Visual Studio, PyCharm,
Komodo, etc.
Alessandro
On 2 mai 2016, at 11:22, 박
see this fix[0]. It has been there for days. Please review it. thanks.
[0] https://review.openstack.org/290238
On Mon, May 2, 2016 at 8:53 AM, Steven Dake (stdake)
wrote:
> Hey folks,
>
> We really need to solve rax-ord in the gate. For awhile it was removed
> because consistently across open
Hi Thierry,
On Mon, May 2, 2016 at 5:45 PM, Thierry Carrez wrote:
> Shinobu Kinjo wrote:
>>
>> I guess, it's usable. [1] [2] [3], probably and more...
>>
>> The reason why still I can just guess is that there is a bunch of
>> documentations!!
>> It's one of great works but too much.
>
>
> We have
Hi Irina,
I fully support the idea of creating separate launchpad project for each
plugin, because plugins have different release cycles and different teams
who support them.
Fuel Plugin documentation [2] has to be updated with information for plugin
developers (how to setup new project) and for
- Mail original -
> De: "Mike Bayer"
> À: "OpenStack Development Mailing List (not for usage questions)"
>
> Envoyé: Jeudi 28 Avril 2016 18:57:59
> Objet: Re: [openstack-dev] [nova] Distributed Database
>
>
>
> On 04/28/2016 08:44 AM, Edward Leafe wrote:
> > On Apr 24, 2016, at 3:28
On 05/02/2016 04:20 AM, 박준하 wrote:
> Hi forks,
>
>
>
> I’m beginner about Openstack developments. I’ve been really interested in
> to know about Openstack and wanted to modify and test it.
>
>
>
> But I’m using PyCharm in the Windows 7 but, It’s very hard to programming
> and testing when I
For reading the code I use Eclipse Mars with PyDev installed on
Windows 7. This allows me to CTRL-click on methods calls to link to
their source, etc. I also use this for some amount of code
modification and can run some amount of unit tests after pip
installing a lot of dependencies. This is mo
On 04/28/2016 07:29 PM, Martinx - ジェームズ wrote:
> Guys,
>
> I'm trying to enable OVS Firewall Driver in my Cloud Env but, it is not
> working...
>
> I'm trying to replace the following line (openvswitch_agent.ini config
> across the cloud):
You also need to set it for mechanism driver. We are tr
On 5/1/16, 10:32 PM, "Swapnil Kulkarni" wrote:
>On Mon, May 2, 2016 at 9:54 AM, Britt Houser (bhouser)
> wrote:
>> Although it seems I'm in the minority, I am in favor of unified repo.
>>
>> From: "Steven Dake (stdake)"
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)
On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote:
> Greetings from Austin!
>
> Yesterday we held the Install Guide planning workgroup. It was a full room,
> with some very robust discussion, and I want to thank everyone for
> participating and sharing their thoughts on this matter.
Hi,
I wrote a quick blog post about what have been discussed during the
summit for Telemetry if you're interested:
https://julien.danjou.info/blog/2016/openstack-summit-newton-austin-telemetry
Feel free to shoot questions if any,
Cheers,
--
Julien Danjou
-- Free Software hacker
-- https://ju
Hi, Shinobu,
Many thanks for the check for Tricircle to be an OpenStack project, and Thierry
for the clarification. glad to know that we are close to OpenStack offical
project criteria.
Let's discuss the initial PTL election in weekly meeting, and start initial PTL
election after that if need
On 05/02/2016 03:05 PM, Steven Dake (stdake) wrote:
On 5/1/16, 10:32 PM, "Swapnil Kulkarni" wrote:
On Mon, May 2, 2016 at 9:54 AM, Britt Houser (bhouser)
wrote:
Although it seems I'm in the minority, I am in favor of unified repo.
From: "Steven Dake (stdake)"
Reply-To: "OpenStack Develop
On 05/02/2016 03:34 PM, Jim Rollenhagen wrote:
On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote:
Greetings from Austin!
Yesterday we held the Install Guide planning workgroup. It was a full room,
with some very robust discussion, and I want to thank everyone for
participating and
>I am in the favor of having two separate repos and evaluating the
>merge/split option later.
>Though in the longer run, I would recommend having a single repo with
>multiple stable deployment tools(maybe too early to comment views but
>yeah)
>
>Swapnil
>Swapnil,
>I gather this is what people wan
Hi QA guys,
We have very few topic this week to discuss. So I think we should skip
this week meeting.
Any thoughts?
Best Regards,
-- Masayuki Igawa
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
I don't have anything urgent so fine with me.
Andrea
On Mon, 2 May 2016, 3:04 p.m. Masayuki Igawa,
wrote:
> Hi QA guys,
>
> We have very few topic this week to discuss. So I think we should skip
> this week meeting.
> Any thoughts?
>
> Best Regards,
> -- Masayuki Igawa
>
> _
Julien,
As mentioned I have been working thru the App Agnostic Parameters blueprint
that will cover review of context attributes and kwarg specific use of
oslo.log.
Presently due to legacy nova usage this current pattern is needed as it.
There was also a discussion at Austin with Michael Still re
It seems for me that we have a dilemma between security (abstaining from
creating a core group which may overuse their rights in kolla repo) and
usability (not having multiple repos, which we experienced badly in the
kolla-mesos era).
I don't find the argument about having k8s ecosystem in sep
On Fri, Apr 22, 2016 at 4:57 PM, Colette Alexander
wrote:
> On Thu, Apr 21, 2016 at 10:42 AM, Doug Hellmann wrote:
>>
>> Excerpts from Colette Alexander's message of 2016-04-21 08:07:52 -0700:
>>
>> >
>> > Hi everyone,
>> >
>> > Just checking in on this - if you're a current or past member of the
This was a good session lead by Robert to fully understand the
repercussions of not ensuring backward compatibility guidelines.
In layman's terms, an Oslo API change made in Mitaka (the last release)
must remain fully backward compatible throughout the entire Newton release
(the current release).
On Mon, May 02, 2016 at 03:52:17PM +0200, Andreas Jaeger wrote:
> On 05/02/2016 03:34 PM, Jim Rollenhagen wrote:
> >On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote:
> >>Greetings from Austin!
> >>
> >>Yesterday we held the Install Guide planning workgroup. It was a full room,
> >>wit
+1 to start kolla-kubernetes work.
- Original Message -
From: "Swapnil Kulkarni"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, May 2, 2016 12:59:40 AM
Subject: Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes
repository management
On 05/02/2016 04:58 PM, Jim Rollenhagen wrote:
On Mon, May 02, 2016 at 03:52:17PM +0200, Andreas Jaeger wrote:
On 05/02/2016 03:34 PM, Jim Rollenhagen wrote:
On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote:
Greetings from Austin!
Yesterday we held the Install Guide planning work
We all had a week full of meetings last week and I'm not sure that we have
anything significantly new on the agenda for the weekly meeting on the 4th.
So, if I don't hear anyone object, I'll send an email out by 4pm Eastern Time
today canceling the Trove weekly meeting for the 4th of May.
Thank
On Thu, Apr 28, 2016 at 01:30:40PM -0500, Sean McGinnis wrote:
> The results are in!
>
> We took a look at the SurveyMonkey results today, and we have now
> formally set the dates and locations for the Cinder Newtone midcycle.
>
> All are welcome and encouraged to attend!
>
> https://etherpad.op
Just a reminder to folk,
I'll send out the summit notes today and get releases going but as we
just had a summit last week, a meeting today on IRC doesn't seem needed
(and most people may not be back yet from the summit anyway),
Have a great week folks (and it was great seeing everyone)!
-Jo
I personally like Openstack Health UI/UX. I use it a lot a an initial
source of information.
Thanks to the OH team for all the great work on this!
And +1 to the new "feedback" link on the top and bottom of every page :)
A few thoughts on my experience with OH.
It can take a few clicks in OH to g
On Mon, May 02, 2016 at 05:12:34PM +0200, Andreas Jaeger wrote:
> On 05/02/2016 04:58 PM, Jim Rollenhagen wrote:
> >On Mon, May 02, 2016 at 03:52:17PM +0200, Andreas Jaeger wrote:
> >>On 05/02/2016 03:34 PM, Jim Rollenhagen wrote:
> >>>On Thu, Apr 28, 2016 at 10:38:13AM -0500, Lana Brindley wrote:
Hi,
Next Vitrage weekly meeting will be held on the coming Wednesday, May 4, at
9:00 UTC.
Agenda:
* Ohad and alexey_weyl will update on Austin Summit and their
presentations[1][2]
* We will start working on Vitrage Newton plan. I opened an etherpad for this
purpose[3], please use it to add
Hi Djimeli,
Thank you for expressing interest in contributing to projects in Glance.
Glance community always welcomes passionate developers to contribute to
our open source and open community platform. It's great to see that
you've participated in GSOC and looking forward to contributing to
OpenSt
I guess this email answers a few questions I asked on my response email
to your interest email. Thanks for clarifying!
On 5/1/16 5:47 AM, Djimeli Konrad wrote:
> Hello,
>
> With respect to my previous mail. I would just like to add that I am
> aware the GSoC2016 and Outreachy2016 application perio
On 05/02/2016 07:38 AM, Matthieu Simonin wrote:
As far as we understand the idea of an ORM is to hide the relational database
with an Object oriented API.
I actually disagree with that completely. The reason ORMs are so
maligned is because of this misconception; developer attempts to use
On Mon, May 2, 2016 at 9:50 AM, Andreas Jaeger wrote:
> On 05/02/2016 03:05 PM, Steven Dake (stdake) wrote:
>> Swapnil,
>>
>> I gather this is what people want but this cannot be done with git and
>> maintain history. To do this, we would have to "cp oldrepo/files to
>> newrepo/files" and the git
On Mon, May 2, 2016 at 10:26 AM, Andrea Frittoli
wrote:
> I personally like Openstack Health UI/UX. I use it a lot a an initial
> source of information.
> Thanks to the OH team for all the great work on this!
>
+1 - This is a really awesome tool. I'll be writing up issues in launchpad
as I enco
What is the difference between "update_allowed" and "immutable" parameters
for a property? According to the plugin guide at
http://docs.openstack.org/developer/heat/developing_guides/pluginguide.html:
update_allowed:
True if an existing resource can be updated, False means update is
accomplished b
Hello guys,
Reading the conversation and analyzing a few trouble that happened with
kolla-mesos and nothing can guarantee that will not happen the same with
the K8S, as well as ensuring that the history will not lost. So, don't
split the repo.
__
One thing we didn't talk about too much at the summit is the part of the spec
that says we will reuse a bunch of ansible stuff to generate configs for the
k8s case...
Do we believe that code would be minimal and not impact separate repo's much or
is the majority of the work in the end going to
During the OpenStack Summit it was decided that getting Grenade to work for
Ironic would be the highest priority for the Ironic project. Because without
Grenade, we won't have upgrade testing and we need upgrade testing for features
we want to land to ensure we don't break anything.
We will be
Thanks for the write up Hongbin and thanks to all those who contributed to the
design summit. A few comments on the summaries below.
6. Ironic Integration:
https://etherpad.openstack.org/p/newton-magnum-ironic-integration
- Start the implementation immediately
- Prefer quick work-around for iden
Also +1 for working on kolla-kubernetes. (Please read this thread if
you haven't yet):
http://lists.openstack.org/pipermail/openstack-dev/2016-May/093575.html
On Mon, May 2, 2016 at 10:56 AM, Ryan Hallisey wrote:
> +1 to start kolla-kubernetes work.
>
> - Original Message -
> From: "Swap
On May 2, 2016, at 10:51 AM, Mike Bayer wrote:
>> Concretely, we think that there are three possible approaches:
>> 1) We can use the SQLAlchemy API as the common denominator between a
>> relational and non-relational implementation of the db.api component. These
>> two implementation could
On 30 April 2016 at 14:24, Fawad Khaliq wrote:
> Hi folks,
>
> Hope everyone had a great summit in Austin and got back safe! :)
>
> At the design summit, we had a Neutron stadium evolution session, which
> needs your immediate attention as it will impact many stakeholders of
> Neutron.
>
It's my
Most of the code is not an overlap. We will preserve the ABI while customizing
the ansible config generation (if we do end up using it). We can use some of
what's in kolla as a starting point.
I'd say the code overlap is a bootstrapping point for the project.
-Ryan
- Original Message -
On 30 April 2016 at 15:42, Doug Wiegley
wrote:
>
> On Apr 30, 2016, at 1:24 PM, Fawad Khaliq wrote:
>
> Hi folks,
>
> Hope everyone had a great summit in Austin and got back safe! :)
>
> At the design summit, we had a Neutron stadium evolution session, which
> needs your immediate attention as i
On 05/02/2016 11:51 AM, Mike Bayer wrote:
On 05/02/2016 07:38 AM, Matthieu Simonin wrote:
As far as we understand the idea of an ORM is to hide the relational
database with an Object oriented API.
I actually disagree with that completely. The reason ORMs are so
maligned is because of this mis
Hi all,
We skipped the meeting today as most of the team is either OOO or
catching-up after summit. We have tentatively cancelled the next week's
meeting as well however, if there is interest I can plan to open the agenda.
--
Thanks,
Nikhil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/01/2016 08:01 PM, Emilien Macchi wrote:
>> If a feature can't land without disruption, then why not using a
>> special branch to be merged once the feature is complete ?
>
> The problem is that during our work, some people will update the
Excerpts from Mike Bayer's message of 2016-05-02 08:51:58 -0700:
>
> Well IMO that's actually often a problem. My goal across Openstack
> projects in general is to allow them to make use of SQL more effectively
> than they do right now; for example, in Neutron I am helping them to
> move a blo
On Mon, May 2, 2016 at 12:22 PM, Armando M. wrote:
>
>
> On 30 April 2016 at 14:24, Fawad Khaliq wrote:
>>
>> Hi folks,
>>
>> Hope everyone had a great summit in Austin and got back safe! :)
>>
>> At the design summit, we had a Neutron stadium evolution session, which
>> needs your immediate atte
Hi Praveen,
The docs you referred to in the plugin guide is for the resource property
attributes - they have nothing to do with parameters. This is an important
distinction because there is also an "immutable" parameter attribute.
The "immutable" property attribute was added because an equiv
Just to clarify my vote.
+1 for single repository
2016-05-02 14:11 GMT-03:00 Jeff Peeler :
> Also +1 for working on kolla-kubernetes. (Please read this thread if
> you haven't yet):
>
> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093575.html
>
> On Mon, May 2, 2016 at 10:56 AM, R
I personally would like to see one set of defaults files for the default
config and merging thereof. (the stuff in roles/*/defaults).
There would be overlap there.
A lot of the overlap involves things like reno, sphinx, documentation,
gating, etc.
During kolla-emsos, separate containers (IIRC) w
On Sun, May 1, 2016 at 5:03 PM, Steven Dake (stdake) wrote:
> I don't think a separate repository is the correct approach based upon one
> off private conversations with folks at summit. Many people from that list
> approached me and indicated they would like to see the work integrated in
> one re
I am looking at
https://www.openstack.org/videos/video/project-kuryr-docker-delivered-kubernetes-next
, around 28:00. You have said that overlay networks are involved, and are
now talking about load balancers. Is this Neutron LBaaS? As far as I
know, a Neutron LBaaS instance is "one-armed"
On 04/26/2016 08:28 AM, Guangyu Suo wrote:
Hello, oslo team
For now, some sensitive options like password or token are configured
as plaintext, anyone who has the priviledge to read the configure file
can get the real password, this may be a security problem that can't
be unacceptable for som
On Tue, Apr 26, 2016 at 4:25 PM, Guangyu Suo wrote:
> I think there is a little misunderstanding over here, the key point about
> this problem is that you store your password as *plaintext* in the
> configuration file, maybe this password is also the password of many other
> systems. You can't st
On Mon, May 2, 2016 at 11:32 AM, Adam Young wrote:
> On 04/26/2016 08:28 AM, Guangyu Suo wrote:
>
> Hello, oslo team
>
> For now, some sensitive options like password or token are configured as
> plaintext, anyone who has the priviledge to read the configure file can get
> the real password, this
On 2016-05-02 17:20:13 +0900 (+0900), �� wrote:
[...]
> But I��m using PyCharm in the Windows 7 but, It��s very hard to
> programming and testing when I tried to change code little bit.
[...]
In my experience, when developing software which runs primarily on
Linux it's a lot more complicated t
On Mon, May 02, 2016 at 11:41:58AM -0700, Morgan Fainberg wrote:
:On Mon, May 2, 2016 at 11:32 AM, Adam Young wrote:
:> Kerberos would work, too, for deployments that prefer that form of
:> Authentication. We can document this, but do not need to implement.
:>
:>
:Never hurts to have alternative
Agreed. A VM running Linux is the only way to really develop for OpenStack.
One could write the code on Windows and share it into the Linux VM to then be
run via tox or another test tool. Both VirtualBox and VMWare support sharing a
folder from your Windows host into the Linux guest.
This way yo
Hi everyone,
When will we name the P release of OpenStack? We named two releases
simultaneously (Newton and Ocata) during the Mitaka release cycle. This
gave us the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata)
releases.
If we were to vote for the name of the P release soon (since the
On 05/02/2016 01:53 PM, Shamail Tahir wrote:
Hi everyone,
When will we name the P release of OpenStack? We named two releases
simultaneously (Newton and Ocata) during the Mitaka release cycle. This
gave us the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata)
releases.
If we were to vot
Just wanted to let people know about the new proposed releases (since
there wasn't a IRC meeting today):
If folks think these need updates or version number changes please
comment on the review (or here).
https://review.openstack.org/#/c/311812/ (the release proposals)
https://review.opensta
+1 to one set of containers for all. If kolla-k8s needs tweaks to the abi, the
request should go to the kolla core team (involving everyone) and discuss why
they are needed/reasonable. This should be done regardless of if there are 1or
2 repo's in the end.
Thanks,
Kevin
On Mon, May 2, 2016 at 2:58 PM, Monty Taylor wrote:
> On 05/02/2016 01:53 PM, Shamail Tahir wrote:
>
>> Hi everyone,
>>
>> When will we name the P release of OpenStack? We named two releases
>> simultaneously (Newton and Ocata) during the Mitaka release cycle. This
>> gave us the names for the
I agree that we need one set of containers. Containers are kolla,
deployment tools are consumers of kolla. We need our containers rock
solid and decoupled from whatever is deploying them. Every company ops
shop have their tooling and methods, let's help them.
I'm not super in favor of ansible spli
Hi team,
As Adrian mentioned, we decided to narrow the scope of the Magnum project, and
needed to revise Magnum’s mission statement to reflect our mission clearly and
accurately. I would suggest to work on this effort as a team and created an
etherpad for that:
https://etherpad.openstack.org/p
At the summit last week, the Swift community spent a lot of time discussing the
feature/hummingbird branch. (For those who don't know, the feature/hummingbird
branch contains some parts of Swift which have been reimplemented in Go.)
As a result of that summit discussion, we have a plan and a goa
Maybe it can help if instead of trying to define criteria to which projects
dont fit into
the stadium, try to define in your spec what IT IS, and for what purpose
its there.
On Mon, May 2, 2016 at 8:53 PM, Kyle Mestery wrote:
> On Mon, May 2, 2016 at 12:22 PM, Armando M. wrote:
> >
> >
> > On
The Citrix XenServer CI is failing on most, if not all, changes it's
running on today. Here is an example failure [1]. Devstack fails to
setup due to a bad package install, so I'm guessing there is a problem
in a mirror being used. I don't know if this is 100% failure but it's
high enough to di
Yup but that didn't happen with kolla-mesos and I didn't catch it until 2
weeks after it was locked in stone. At that point I asked for the ABI to
be unified to which I got a "shrug" and no action.
If it has been in one repo, everyone would have seen the multiple ABIs and
rejected the patch in th
Jeff,
What you propose is reasonable, but the timeline to make all that long
term vision happen is time consuming and we want to get rolling now, not
in t-4 to 6 weeks after we can sort out a kolla-docker and kolla-ansible
split.
FWIW It will make backporting a serious painful experience, and I a
On Mon, May 2, 2016 at 1:23 PM, Jeff Peeler wrote:
> On Sun, May 1, 2016 at 5:03 PM, Steven Dake (stdake) wrote:
>> I don't think a separate repository is the correct approach based upon one
>> off private conversations with folks at summit. Many people from that list
>> approached me and indicat
The Trove weekly meeting on the 4th of May is canceled. We can pick up any
conversations that we need on IRC as required.
Thanks,
-amrith
> -Original Message-
> From: Amrith Kumar [mailto:amr...@tesora.com]
> Sent: Monday, May 02, 2016 11:14 AM
> To: OpenStack Development Mailing List (
+1 for kolla-kubernetes.
On Mon, May 2, 2016 at 1:07 PM, Mauricio Lima wrote:
> Just to clarify my vote.
>
> +1 for single repository
>
> 2016-05-02 14:11 GMT-03:00 Jeff Peeler :
>>
>> Also +1 for working on kolla-kubernetes. (Please read this thread if
>> you haven't yet):
>>
>> http://lists.ope
Sorry for top-post...
There's a third option : Using Feature branch for Kubernetes with a
custom gerrit group
* Feature branch can be sync'ed from Master periodically
* Feature branch can have it's own separate gerrit group.
* We can opt to merge from feature branch to master if necessary.
* We c
On Mon, May 2, 2016 at 3:18 PM, Gal Sagie wrote:
> Maybe it can help if instead of trying to define criteria to which projects
> dont fit into
> the stadium, try to define in your spec what IT IS, and for what purpose its
> there.
Well said. This came up multiple times in the Gerrit discussion(s)
On 05/01/2016 05:03 PM, Steven Dake (stdake) wrote:
Ryan had rightly pointed out that when we made the original proposal
9am morning we had asked folks if they wanted to participate in a
separate repository.
In Keystone, we are going to more and more repositories all the time.
We started wit
The Nova team held unconference sessions on Wednesday and Thursday after
the lunch break. An unconference session is a 40 minute session broken
into 10 minute talks/proposals for a blueprint/spec/feature idea. It's
for things that need some discussion but don't warrant a full session,
generally
On Mon, May 2, 2016 at 12:38 PM, Steven Dake (stdake)
wrote:
> Yup but that didn't happen with kolla-mesos and I didn't catch it until 2
> weeks after it was locked in stone. At that point I asked for the ABI to
> be unified to which I got a "shrug" and no action.
>
> If it has been in one repo,
Hi team,
We cancelled the meeting today as most of the team is either OOO or in vacation
after summit. We may also cancel the next meeting if there is no topic raised.
Thanks.
--
Cheers & Best regards,
Fei Long Wang (王飞龙)
Were we looking at the same etherpad? I think the ‘inclusion criteria’ and
‘benefits of the proposal’ sections cover those two points. Are you referring
to something else?
Thanks,
doug
> On May 2, 2016, at 12:18 PM, Gal Sagie wrote:
>
> Maybe it can help if instead of trying to define crite
Hi, octavia guys,
Recently, We have been thinking about deploying octavia into
production (pre-production first in our case). Here are some
questions/concerns that need your suggestions and feekback.
1. Octavia will use a default instance flavour, which is
pre-configured, to create amphorae. Do y
On 05/02/2016 02:53 PM, Shamail Tahir wrote:
Hi everyone,
When will we name the P release of OpenStack? We named two releases
simultaneously (Newton and Ocata) during the Mitaka release cycle. This gave us
the names for the N (Mitaka), N+1 (Newton), and N+2 (Ocata) releases.
If we were to vot
This patch removed the ./rejoin-stack.sh script:
https://review.openstack.org/#/c/291453/
I relied on this heavily in my development VM which sees lots of restarts
because of various things (VM becomes unresponsive in load testing, my
laptop has a kernel panic, etc). Normally this was not a big de
Hi,
For those of you who are interested, you could find our slide at
http://www.slideshare.net/zhipengh/storage-is-not-virtualized-enough-part-2-lets-do-service-chaining
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangz
Thanks for asking this, I would also like to know what the “real” answer is.
But what I’ve found myself doing recently, since it was unwise to 100% count on
rejoin-stack.sh, was to “do” everything via scripts and take periodic backups
of same. You’re still only one power outage away from losing
Honestly those kind of major changes have to be discussed very carefully.
On Tue, May 3, 2016 at 7:10 AM, Kevin Benton wrote:
> This patch removed the ./rejoin-stack.sh script:
> https://review.openstack.org/#/c/291453/
>
> I relied on this heavily in my development VM which sees lots of restarts
Hi Lingxian,
For #1, we create a nova flavor for the amphora in the devstack
plugin. It is currently:
nova flavor-create --is-public False m1.amphora
${OCTAVIA_AMP_FLAVOR_ID} 1024 2 1
I have not done extensive testing with these settings to optimize it.
We were shooting for the minimum viable co
Well, I don't think we should rely on ansible's config generation. We
can't really as it's wired into ansible too much. jinja2 templates in
Dockerfiles aren't connected to ansible in any way and are perfectly
reusable.
On 2 May 2016 at 16:13, Qiu Yu wrote:
> On Mon, May 2, 2016 at 12:38 PM, Steve
Hello everyone,
It was great to meet you (those who were) at the summit and missed those
who couldn't come. So, for those who are waiting for updates I wanted to
share some awareness of what's coming in the next few weeks.
* I will be sending summaries of individual discussion items from the
summ
Hello everyone,
Just wanted to send a brief summary of the discussions at the summit.
This list is not holistic however, it covers the relevant aspects that
various stakeholders need to be aware of.
* Glare is useful for different use cases in OpenStack including
currently being asked for i
Added a few more tags to the subject line.
On 5/2/16 7:05 PM, Nikhil Komawar wrote:
> Hello everyone,
>
> Just wanted to send a brief summary of the discussions at the summit.
> This list is not holistic however, it covers the relevant aspects that
> various stakeholders need to be aware of.
>
>
Hello everyone,
Just wanted to send a brief summary of the discussions at the summit.
This list is not holistic however, it covers the relevant aspects that
various stakeholders need to be aware of.
* Image sharing in it's current state is inadequate for the
requirement of sharing an Image
Hello! I enjoyed very much listening in on the default token provider
work session last week in Austin, so thanks everyone for participating
in that. I did not speak up then, because I wasn't really sure of this
idea that has been bouncing around in my head, but now I think it's the
case and we sho
Hello everyone,
Just wanted to send a brief summary of the discussions at the summit.
This list is not holistic however, it covers the relevant aspects that
various stakeholders need to be aware of.
* The current proposal is for centralizing config options, improving
help text, adding depen
1 - 100 of 122 matches
Mail list logo
