I noticed this thread by Monty's reply. Sorry for my late :(
I think we need to think 'id' separately for API modeling and DB modeling.
In the API perspective, one of the important things is that 'id' is
not predictable
and it rarely conflict. From this perspective, UUID works.
In the DB perspec
Tag is assigned per node basis and it is local to a node.
so ports on different nodes usually have different tags.
2017年4月3日(月) 18:19 Vikash Kumar :
> Hi Gary,
>
>Thanks for pointing the source code. Does this has RFE ? I see for
> ports of same network, have different tags on different compu
Hi,
I would like to raise a topic when horizon nova-network support can be dropped.
I added [tc] tag as it is related to
"assert:follows-standard-deprecation" tag in the governance.
Can horizon drop nova-network support based on the deprecation of nova-network
from the nova team?
or does horizon
2017-03-17 5:50 GMT+09:00 Ihar Hrachyshka :
> On Thu, Mar 16, 2017 at 12:00 PM, Doug Hellmann wrote:
>> Please keep translations for exceptions and other user-facing messages,
>> for now.
>
> To clarify, that means LOG.exception(_LE(...)) should also be cleaned
> up? The only things that we should
+1
2017-02-17 14:18 GMT-05:00 Kevin Benton :
> Hi all,
>
> I'm organizing a Neutron social event for Thursday evening in Atlanta
> somewhere near the venue for dinner/drinks. If you're interested, please
> reply to this email with a "+1" so I can get a general count for a
> reservation.
>
> Cheer
2017-01-07 4:10 GMT+09:00 Sean Dague :
> It's a new year, and in anticipation of having a productive time in
> Atlanta around the service catalog, I refreshed the set of patches from
> last year around starting to stub out a service-types-authority -
> https://review.openstack.org/#/c/286089/
>
>
I have the same opinion as Kevin,
UI support for a feature in the neutron repo should be in the main horizon
repo.
I believe this improves usability too.
If I have a neutron deployment (it is a typical deployment now),
I would like to use neutron feature support only after installing the main
hori
+1
2016-12-14 10:22 GMT+09:00 Armando M. :
> Hi folks,
>
> Abhishek Raut's recent involvement in OSC and python-neutronclient has
> helped moving a few efforts along in the right direction. I would like to
> suggest we double down on core firepower for the neutronclient repo
> alongside Akihiro [
I totally agree with the direction of OSC and shade.
The similar discussion happens in neutronclient side before too.
>From user perspective, 'name' is really useful to identify resources,
even though admin usually use ID to identify resources.
In the past neutronclient discussion, requiring at le
+1
2016-11-14 9:24 GMT+09:00 Richard Jones :
> Hi Horizon core team,
>
> I propose Kenji Ishii as a new Horizon core reviewer. Kenji has been a
> solid Horizon contributor for some time, with thoughtful and helpful
> reviews showing good judgment and good knowledge of Horizion and
> related syste
Hi,
I noticed strings in tests (unit tests or others) have translation marks
(_, _LE and so on).
Do we need translation marks for them?
I don't think so for most cases from various reasons below.
Only exception is to test translations.
>From translators:
- Effort to translate strings in tests le
.
2016-09-23 9:30 GMT+09:00 Akihiro Motoki :
> Hi horizoners,
>
> The current horizon gate is half broken as both integrated tests are
> 30-40% failure rate.
> (See https://bugs.launchpad.net/horizon/+bug/1626536 and
> https://bugs.launchpad.net/horizon/+bug/1626643)
> Fixes f
Hi horizoners,
The current horizon gate is half broken as both integrated tests are 30-40%
failure rate.
(See https://bugs.launchpad.net/horizon/+bug/1626536 and
https://bugs.launchpad.net/horizon/+bug/1626643)
Fixes for these bugs are now under the gate.
Please avoid using 'recheck' if one of in
Thanks. After I sent the mail, we had a good conversation with Rabi and
understood the whole background.
Horizon will try to support better keystone v3 support in Ocata cycle.
2016-09-21 22:47 GMT+09:00 Zane Bitter :
> On 21/09/16 03:30, Akihiro Motoki wrote:
>
>> Hi,
>&
Hi,
The default policy.json provided by heat limits 'service-list' API to
'admin' project like below.
Is there any reason 'admin' role user in non-'admin' project cannot
see service-list?
"service:index": "rule:context_is_admin",
"context_is_admin": "role:admin and is_admin_project:True",
I think It is time to merge the wiki into horizon devref.
It is not a good situation that we have two contents.
2016-09-20 17:01 GMT+09:00 Rob Cresswell :
> As you've noticed, this doc isn't updated currently. The current browsers
> supported are listed here:
> http://docs.openstack.org/developer/
Hi Ian,
gettext itself allows this pattern [1] but django compilemessage
expects variables with same names are used in all plural forms (See
Note in [2]).
IMHO it is better to use same variables in all plural forms in code as
possible as we can.
As translator, I try to use the second pattern (i.e.
2016-09-09 12:43 GMT+09:00 Lana Brindley :
> Hi everyone,
>
> Only four weeks to go until Newton! Andreas, Brian, Olga, and I met with our
> new release managers Olena and Alex a few days ago, and we're all ready and
> waiting with bated breath to get started on the release. Don't forget that
>
2016-09-06 22:02 GMT+09:00 Ihar Hrachyshka :
> Akihiro Motoki wrote:
>
>> What releases should we support in API references?
>> There are several options.
>>
>> 1. The latest stable release + master
>> 2. All supported stable releases + master
>> 3. more
What releases should we support in API references?
There are several options.
1. The latest stable release + master
2. All supported stable releases + master
3. more older releases too?
Option 2 sounds reasonable to me.
This question is raised in the neutron api-ref patch [1].
This patch drops t
2016-09-05 16:03 GMT+09:00 Andreas Jaeger :
> On 09/05/2016 07:45 AM, Tony Breeds wrote:
>> On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote:
>>> Reviewing all the constraints work, I see that repositories have created
>>> some workaround around requirements install for one of these t
In the neutronclient check queue,
gate-neutronclient-test-dsvm-functional is broken now [1].
Please avoid issuing 'recheck'.
[1] https://bugs.launchpad.net/python-neutronclient/+bug/1616749
__
OpenStack Development Mailing Li
Hi Neutron team,
As you may know, the OpenStack API references have been moved into
individual project repositories, but it contains a lot of wrong
information now :-(
Let's clean up API reference.
It's now time to start the clean up and finish the cleanup by Newton-1.
I prepared the etherpad pa
2016-08-13 7:36 GMT+09:00 Anne Gentle :
>
>
> On Fri, Aug 12, 2016 at 3:29 AM, Akihiro Motoki wrote:
>>
>> this mail focuses on neutron-specific topics. I dropped cinder and ironic
>> tags.
>>
>> 2016-08-11 23:52 GMT+09:00 Anne Gentle :
>> >
>&g
this mail focuses on neutron-specific topics. I dropped cinder and ironic tags.
2016-08-11 23:52 GMT+09:00 Anne Gentle :
>
>
> On Wed, Aug 10, 2016 at 2:49 PM, Anne Gentle
> wrote:
>>
>> Hi all,
>> I wanted to report on status and answer any questions you all have about
>> the API reference and g
2016-07-29 18:34 GMT+09:00 Ihar Hrachyshka :
> Cathy Zhang wrote:
>
>> Hi Ihar and all,
>>
>> Yes, we have been preparing for such a release. We will do one more round
>> of testing to make sure everything works fine, and then I will submit the
>> release request.
>> There is a new patch on "stadi
Hi Neutron folks,
As you may know, the OpenStack API references have been moved into
individual project repositories.
For the networking API, we have the api-ref document in neutron-lib repository.
The api-ref document imported into neutron-lib repository needs to be
cleaned up.
I would like to p
Do we need to use both UpgradeImpact flag in commit messages and
'upgrade' section in reno?
Many projects now use reno and reno has 'upgrade' section to inform
operators/users of upgrade impact changes.
I wonder we still need to use UpgradeImpact flag in commit messages.
Akihiro
Hi,
If I understand correctly, what you need is to expose the neutron
behavior through API or something. In this particular case, neutron
need to send a vif-plugged event when neutron detects some event in
the data plane (VIF plugging in OVS or some virtual switch). Thus I
think the question can b
Henry is talking about drivers which CURRENTLY support networking-sfc.
In my understanding, ODL driver for networking-sfc is ongoing.
2016-05-23 13:22 GMT+09:00 Elzur, Uri :
> ODL has support for sfc w NSH. Why would ONOS count as backend and ODL not?
>
> Uri
>
> Sent from my iPhone
>
> On May 21,
Hi Sukhdev, Dave,
I think this backport is acceptable.
In Kilo release, neutron is in a middle way of splitting vendor codes
to separate repositories.
The master fix is available at https://review.openstack.org/#/c/309622/ and
as far as I checked, stable/kilo fix are split into two parts:
- netwo
n Austin we had a session on the future of neutron client and
discussed the CLI transition to OpenStack Client (OSC).
The session etherpad is found at [1].
* We checked the progress of OSC transition and it is good.
Support of 11 resources which are targets of the initial effort.
In Newton cyc
From: Paul Carver [mailto:pcar...@paulcarver.us]
> Sent: Tuesday, April 26, 2016 10:20 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project
> f2f2 meet-up place and time
>
> On 4/26/2016 00:35, Akihiro Motoki wrote:
>&g
+1
Thanks for coordinating!
2016-04-25 10:55 GMT-05:00 Kyle Mestery :
> Ihar, Henry and I were talking and we thought Thursday night makes sense for
> a Neutron social in Austin. If others agree, reply on this thread and we'll
> find a place.
>
> Thanks!
> Kyle
>
> _
It is neutron related topic. I added [neutron] tag to the subject.
2016-04-26 7:19 GMT-05:00 Na Zhu :
> Dear All,
>
>
> I have a question about OSC transition, recently, the community approves
> moving bgp out of neutron, as a service like other *aas. The BGP CLIs need
> be removed from neutroncli
Hi Cathy and folks interested in SFC and classifers!
Can't we use a different room like Salon D?
Salon C is a lunch room and at that time there are no sessions in other rooms.
It would be great if we can use Salon D or E (after looking at the
first day's session)
I think we can gather more easily
Neutron already supports L3 router with network namespaces which send
notifications, as Armando mentioned.
Ceilometer can consume these notification and I think monisca can do
similar things.
I believe you can collect enough information for neutron ovs implementation.
2016-04-25 13:20 GMT-05:00 Ru
2016-04-20 14:53 GMT+09:00 Ihar Hrachyshka :
> Ian Wells wrote:
>
>>
>> Right. Note that custom MTU works out of the box only starting from
>> Mitaka.
>>
>> It's been in from at least Kilo (give or take a some bugfixes, it seems,
>> all of which deserve backporting).
>
>
> It never worked as you w
Hi,
I noticed Mitaka release notes for neutron *-aas [1,2,3] are not
referred to from anywhere.
Neutron has four deliverables (neutron, lbaas, fwaas, vpnaas),
but only the release note of the main neutron repo is linked.
Is the right solution to add links to the main neutron release notes?
Anothe
2016-04-18 15:58 GMT+09:00 Ihar Hrachyshka :
> Sławek Kapłoński wrote:
>
>> Hello,
>>
>> What MTU have You got configured on VMs? I had issue with performance on
>> vxlan network with standard MTU (1500) but when I configured Jumbo
>> frames on vms and on hosts then it was much better.
>
>
> Right
It's been over a week.
I'd like to welcome Hirofumi to the neutron core reviewer team!
Akihiro
2016-04-08 13:34 GMT+09:00 Akihiro Motoki :
> Hi Neutrinos,
>
> As the API Lieutenant of Neutron team,
> I would like to propose Hirofumi Ichihara (irc: hichihara) as a me
Hi Neutrinos,
As the API Lieutenant of Neutron team,
I would like to propose Hirofumi Ichihara (irc: hichihara) as a member of
Neutron core reviewer team mainly focuing on the API/DB area.
Hirofumi has been contributing neutron actively in the recent two
releases constantly.
He was involved in ke
Hi,
# subject should be more specific.
There is no reason to implement them.
Unfortunately there is no contribution so far :)
This is the list for developers.
Do you want to implement them?
2016-04-06 15:37 GMT+09:00 李戈 :
> HI,
> I am a openstack user. But when I use load balance and firewa
Hi Serg,
I proposed another way to sahara-dashboard [1].
This is the way used in neutron sub-projects.
It also allows us to use constrained environments used in OpenStack gate jobs.
I believe it works for all horizon related projects.
I agree the simplest way is to publish horizon to PyPI, but
th
2016-03-18 12:06 GMT+09:00 reedip banerjee :
> Dear All Neutron Developers and Reviewers,
>
> I have a query/concern related to the parsing of options in
> python-neutronclient.
> I would like to bring this up, as it "may" also impact the transition of the
> CLIs to the openstack client as well.
>
IIRC 'Quantum' was renamed to 'Neutron' due to the trademark issue.
I don't think reverting it to 'Quantum' resolves the issue.
When we chose a new name, the foundation checked the legal/trademark issue,
so I think it is better to contact the OpenStack foundation or discuss
it in the legal-discuss
Thank you all for your supports.
We can see the progress of translations at [0]
Shu,
Magnum UI adopts the independent release model. Good to know you have
stable/mitaka branch :)
Once the stable branch is cut, let not only me but also the i18n team know it.
openstack-i18n ML is the best place to d
2016-03-22 20:08 GMT+09:00 Doug Hellmann :
>
>> On Mar 22, 2016, at 6:18 AM, Akihiro Motoki wrote:
>>
>> Hi release management team,
>>
>> Can we have a new release of django-openstack-auth from stable/mitaka
>> branch for translations?
>>
>&g
Hi release management team,
Can we have a new release of django-openstack-auth from stable/mitaka
branch for translations?
What is happening?
django-openstack-auth is a library project consumed by Horizon.
The (soft) string freeze happens when the milestone-3 is cut.
The milestone-3 is also the d
Hi dashboard plugins team
(sahara-dashboard, trove-dashboard, magnum-ui, murano-dashboard)
As Horizon i18n liaison, I would like to have a consensus on a rough schedule
of translation import for Horizon plugins.
Several plugins and horizon itself already released RC1.
For Horizon translation, we
+1 from me too!
2016-03-11 17:38 GMT+09:00 Tatiana Ovtchinnikova :
> +1. Thanks for your contribution!
>
>
>
> 2016-03-11 6:40 GMT+03:00 Zhenguo Niu :
>>
>> +1 from me, thanks for all the hard work!
>>
>> On Thu, Mar 10, 2016 at 3:27 AM, Michael Krotscheck
>> wrote:
>>>
>>> +1. Another vote in fa
2016-03-09 7:43 GMT+09:00 Armando M. :
>
>
> On 8 March 2016 at 15:07, Doug Hellmann wrote:
>>
>> Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700:
>> > Hi folks,
>> >
>> > There's a feature or two that are pending to be delivered in Mitaka
>> > [1,2],
>> > and those involve changes
One thing to note.
The role of i18n liaison is not to keep it well translated.
The main role is in a project side,
for example, to encourage i18n related reviews and fixes, or
to suggest what kind of coding is recommended from i18n point of view.
Akihiro
2016-03-02 12:17 GMT+09:00 Shuu Mutou :
>
2016-02-27 1:02 GMT+09:00 Sean Dague :
> On 02/26/2016 10:52 AM, Chris Dent wrote:
>> On Fri, 26 Feb 2016, Jay Pipes wrote:
>>> On 02/26/2016 09:02 AM, Akihiro Motoki wrote:
>>>> We can create a tag by PUT'ing an individual tag:
>>>> What status cod
Thanks Jay.
I will send an update to api-wg repo as well.
2016-02-27 0:36 GMT+09:00 Jay Pipes :
> On 02/26/2016 09:02 AM, Akihiro Motoki wrote:
>>
>> Hi API-WG,
>>
>> Neutron is implementing tag support for network resource [0].
>> The implementation follows
Hi API-WG,
Neutron is implementing tag support for network resource [0].
The implementation follows 'Tags' guideline defined by API-WG [1].
I have a questions on the guideline.
We can create a tag by PUT'ing an individual tag:
What status code should be returned if a requested tag already e
t; for Horizon project ?
>
> Best regards
> Ying Chun Guo (Daisy)
>
>
> Akihiro Motoki wrote on 2016/02/26 01:00:15:
>
>> From: Akihiro Motoki
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Date: 2016/02/26 01
rg/project/view/designate-dashboard
Thanks for the follow-up.
Yeah. I typed designate-dashboard and made a mistake :-(
>
>> Whether these projects can get translated in Mitaka depends.
>> Let's discuss with team.
>
> Andreas
>
>> Best regards
>> Ying Chun Gu
Hi Shu,
I am confused with the sentence "My Zanata ID "shu" is used by "Seihu"
in Launchpad".
I think Zanata ID is linked with OpenStack Foundation profile
and is not linked directly with launchpad ID.
Could you clarify the situation?
2016-02-25 18:08 GMT+09:00 Shuu Mutou :
> Hi,
>
> Stackalyti
cliff-based client including neutronclient and openstackclient
supports various formatters.
I don't think it is a good idea to depend on the output of 'table' formatter.
My understanding is 'table' formatter (the default formatter) is for
human readability.
IMHO it is better to use json formatter o
Hi Daisy,
AFAIK the following horizon plugins are ready for translation.
I tested and confirmed translations of these two work well with Japanese.
A minor improvement on devstack or other stuff are in progress but it
does not affect translation.
* trove-dashboard
* sahara-dashboard
The following
Sorry for chiming in late.
It sounds natural to me that when no --nic option is specified and no
neutron network exists 'get-me-a-network' feature is used.
After a network for a project is created by a get-me-a-network or when
a project already has one network,
a user do not need to specify --nic
Hi sahara-dashaboard team (perhaps horizon and sahara dev team),
I am working on translation support in sahara-dashboard for feature
parity of Liberty horizon.
TL;DR: Why does not sahara-dashboard use 'sahara_dashboard' as INSTALLED_APPS?
Can't we add 'sahara_dashboard' as INSTALLED_APPS?
Long v
Hi,
> Horizon still have some things we need to tidy up on our end to make sure we
> have full support for testing and localization for external plugins.
I am pleased to announce that translations of trove-dashboard and
sahara-dashboard
now work for the master branch. We have the parity to Libert
I don't think you need to bump the major version per OpenStack release.
If the functionalities is backward-compatible, from the context of the
semantic versioning
you don't need to bump the major version, i.e. 1.x.y to 2.x.y.
According to your description, Mitaka version can be 1.1.0.
I am not sure
I agree that the current definition can be improved.
"Provider Network" vs "Self service network" highlights who can
provision a network.
In my understanding, "Provider Network" is a network provisioned by
the cloud operator. Practically the operator cannot provision a network
for a tenant, so a
2016-01-19 18:58 GMT+09:00 Kekane, Abhishek :
>
>
> -Original Message-
> From: Andreas Jaeger [mailto:a...@suse.com]
> Sent: 19 January 2016 15:19
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all][clients] Enable hacking in python-*clien
Hi Abishek,
In my understanding, hacking check is enabled for most (or all) of
python-*client.
For example, flake8 is run for each neutronclient review [1].
test-requirements installs hacking, so I believe hacking check is enabled.
openstackclient and novaclient do the same [2] [3].
Am I missing s
devstack creates /etc/openstack/clouds.yaml (os-client-config
configuraiton files) which specifies to use keystone v3.
neutronclient supports os-client-config and keystoneauth which handles
the difference of keystone API.
Note that clouds.yaml is very convenient way to use OpenStack CLI [1].
As Mi
Hi,
# cross-posting to -dev and -operators ML
In the current most OpenStack implementation,
when we use LOG.exception, we don't pass an exception message to LOG.exception:
LOG.exception(_LE("Error while processing VIF ports"))
IIUC it is because the exception message will be logged at the end
A series of os-client-config integration for neutronclient are proposed.
Several questions hit me during reviewing
https://review.openstack.org/#/c/242096.
It is a review of neutroncleint, but I think it is generic to all CLIs.
(1) global option vs command-specific option
Various python-*client
I added 'oslo' and 'cliff' subject tag as well.
2015-12-31 1:37 GMT+09:00 Sofer Athlan-Guyot :
> Hi,
>
> I have added neutron people as they may help to find a solution.
>
> After banging my head against the wall for a whole afternoon I
> discovered a serious bug in puppet neutron module.
>
> I no
I haven't looked into the code detail, but as far as I read
https://docs.djangoproject.com/en/1.9/topics/i18n/translation/#specialties-of-django-translation
it is enforced by django framework.
How django searches message catalogs is described at
https://docs.djangoproject.com/en/1.9/topics/i18n/tr
GMT+09:00 Akihiro Motoki :
> Thanks all.
> All comments so far are from neutron side. I would like to wait inputs
> from horizon side, especially David.
>
> Option (c) is what we do in neutron sub-projects under neutron stadium model
> and
> I agree it makes sense and soun
Hi Gal,
One simple way is to get credentials from clouds.yaml (through
os-client-config).
devstack prepares clouds.yaml (~/.config/openstack/clouds.yaml) which contains
both devstack-admin (admin) and devstack (demo) account.
neutronclient functional test is a good example.
http://git.openstack.o
Thanks for the replies.
I totally agree that we should deprecate it.
We forgot to mark --request-format as deprecated.
The way we should go is to deprecate --request-format.
Akihiro
2015-12-07 21:24 GMT+09:00 Neil Jerram :
> On 07/12/15 12:01, Akihiro Motoki wrote:
>> Hi,
>>
>
Hi,
neutronclient is now dropping XML support and as a result
"--request-format" option is no longer needed as JSON is the only format now.
What is the recommended way for options no longer needed?
Does bumping major version of CLI allow us to drop an option without
deprecation?
- Deprecate such
Thanks all.
Let's drop XML support from neutronclient!
Elena already posted a patch to drop it.
Akihiro
2015-12-04 1:48 GMT+09:00 Armando M. :
>
>
> On 3 December 2015 at 08:33, Ihar Hrachyshka wrote:
>>
>> Akihiro Motoki wrote:
>>
>>> Hi,
>>>
2015-12-05 8:40 GMT+09:00 Armando M. :
>
>
> On 4 December 2015 at 11:22, Henry Gessau wrote:
>>
>> Sean M. Collins wrote:
>> > I've noticed that a lot of features are now being documented as RSTs
>> > inside of devref. Like the following:
>> >
>> > https://review.openstack.org/#/c/251859/
>> >
>
Hi,
python-neutronclient recently added reno support and
I added the reno directive " . release-notes::" to the neutronclient
documentation.
As a result, this prevents users from building the documentation from
released tarballs
using 'python setup.py build_sphinx' because the reno module expects
Hi,
python-neutronclient still has XML support of Neutron API.
I would like to discuss when we drop XML support in neutronclient.
Neutron API XML suppoort was marked as deprecated in Icehouse and Juno
and was dropped in Kilo. Juno is now EOL and we have no gate testing which
requires XML support.
hiro
2015-11-25 14:46 GMT+09:00 Akihiro Motoki :
> Hi,
>
> Neutron has now various subprojects and some of them would like to
> implement Horizon supports. Most of them are additional features.
> I would like to start the discussion where we should have horizon support.
>
>
Hi,
Neutron has now various subprojects and some of them would like to
implement Horizon supports. Most of them are additional features.
I would like to start the discussion where we should have horizon support.
[Background]
Horizon team introduced a plugin mechanism and we can add horizon panels
it sounds a good idea in general.
One question is how each project team should handle DocImpact bugs
filed in their own project.
It will be a part of "Plan and implement an education campaign"
mentioned in the docs spec.
I think some guidance will be needed. One usual question will be which
guide(
In the current AddRule form, validate_port_range is used as a validator,
so a value from 1 to 65535 is accepted.
I think this is the reason that _clean_rule_icmp check the exact value range.
You can improve it as you think.
bug 1511748 is a regression of validate_port_range change in
https://revie
I missed this mailing thread. Thanks for coordinating the effort!
Mon 1500UTC works for me too.
2015-11-18 23:36 GMT+09:00 Ihar Hrachyshka :
> Thanks everyone for responses.
>
> It seems like Mon 15:00 UTC works for all of us, so I pushed the following
> patch to book #openstack-meeting-2 room wee
Could you share the exact place of the installation guide?
I would like to check it.
Are you talking about the network node?
I think these settings are required when you configure a network node
without network namespace.
If we use network namespace in a network node, I don't think we need
these
2015-11-05 21:30 GMT+09:00 Gal Sagie :
> The current OVS binding proposals are not for nested containers.
> I am not sure if you are asking about that case or about the nested
> containers inside a VM case.
>
> For the nested containers, we will use Neutron solutions that support this
> kind of con
Hi Antonio,
What you need to do is just to go.
There is no need for sign up now.
2015-10-26 4:17 GMT+09:00 Tonhão - Antonio Brasolin :
> Hi. What do I have to do to go to this meeting? Do I have to sign up
> somewhere? Thanks.
>
> On Fri, Oct 23, 2015 at 2:23 PM, Akihiro Motoki wro
Hi Neutron folks,
We are pleased to announce Neutron social meet-up in Tokyo.
Thanks Takashi and Hirofumi for the big help.
I hope many of you will be there and enjoy the time.
If you have made RSVP, don't miss it!
We recommend to join the beginning, but come and join us even if you
arrive late.
I resent my mail as I forgot to add [Horizon] tag.
2015-10-22 23:50 GMT+09:00 Akihiro Motoki :
> Hi Horizon team,
>
> Doug and I are planning a horizon social meetup in Tokyo.
> As you may know, it is planned on Monday Oct 26.
>
> 10/26 20:00 -
> Torikaku at Shinagawa Inter
Hi Horizon team,
Doug and I are planning a horizon social meetup in Tokyo.
As you may know, it is planned on Monday Oct 26.
10/26 20:00 -
Torikaku at Shinagawa Intercity (とりかく 品川インターシティ店)
The location is:
https://www.google.com/maps/place/Kineya+Shinagawa+Inter+City/@35.6269353,139.742403,15z/da
Hi team,
Recently there are many patches to add help messages to neutron
*-update sub-commands
(or others). I made similar comments and discussions repeatedly in
various reviews.
I created a etherpad page [1] to dicsuss neutronclient options
Once we collect opinions and have a consensus,
I will
Hi Cinder team,
What is the expected service name of Cinder v2 API in keystone catalog?
DevStack configures "volumev2" for Cinder v2 API by default.
Can we "volume" for Cinder v2 API or do we always need to use "volumev2"
in deployments with only Cinder v2 API (i.e. no v1 API) ?
The question was
2015-10-14 0:14 GMT+09:00 Doug Hellmann :
> Excerpts from Thomas Goirand's message of 2015-10-13 12:38:00 +0200:
>> On 10/12/2015 11:09 PM, Steve Baker wrote:
>> > On 13/10/15 02:05, Thomas Goirand wrote:
>> >>
>> >> BTW, the same applies for tablib which is in a even more horrible state
>> >> that
Hi,
2015-10-05 15:54 GMT+09:00 Gary Kotton :
> Hi,
> Yes, you are correct. That patch is the culprit (my bad and once again
> humble apologies)
>
> Regarding the AZ support I think that we need to do the following:
>
>1. Have this in a separate topic until it is complete. I have a number
>
atest-kilo-28-09-2015-masoom:/opt/stack/devstack#
>> neutron port-update 2d1bfe12-7db6-4665-9c98-6b9b8a043af9
>> --allowed-address-pairs [10.0.0.201] action=clear
>> The number of allowed address pair exceeds the maximum 10.
>>
>> root@openstack-latest-kilo-28-09-
As already mentioned, we need to pass [] (an empty list) rather than None
as allowed_address_pairs.
At the moment it is not supported in Neutron CLI.
This review https://review.openstack.org/#/c/218551/ is trying to fix this
problem.
Akihiro
2015-09-28 15:51 GMT+09:00 shihanzhang :
> I don't s
For Horizon, the fix is now in the gate queue.
https://review.openstack.org/#/c/218786/
It only skips the related test, but the failing test is specific to vendor
plugin implementation
and we can explore the fix later.
Regarding the stable releases, Horizon may also need the similar version
cap fo
As Mathias said, Horizon worked (and in many cases works) cross releases.
Horizon determines supported features based on keystone catalogs,
extension list from back-end services (like nova, neutron).
Micro-versioning support may come in future (though it is not supported).
For backward incompatib
101 - 200 of 322 matches
Mail list logo
