+1 for both.
On 2016年11月08日 03:06, Adrian Otto wrote:
Magnum Core Team,
I propose Jaycen Grant (jvgrant) and Yatin Karel (yatin) as new Magnum Core
Reviewers. Please respond with your votes.
Thanks,
--
Best Regards,
Eli Qiao (乔立勇), Intel OTC.
://review.openstack.org/#/c/357207
-Original Message-
From: taget [mailto:qiaoliy...@gmail.com]
Sent: Thursday, August 18, 2016 5:08 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Cc: Qiao, Liyong <liyong.q...@intel.com>; Bhati
hi neutron ovo hacker:
Recently I am working on neutron OVO blue print, and found there are
some blocking (slow progress) issues when tring
to add new object to Neutron.
When I try to add Flavor related object on [1], I need to add 2
foreign_keys to FlavorServiceProfileBinding :
flavor_id:
+1 for both, they would be great addition to zun team.
On 2016年08月12日 10:26, Yanyan Hu wrote:
Both Sudipta and Wenzhi have been actively contributing to the Zun
project for a while. Sudipta provided helpful advice for the project
roadmap and architecture design. Wenzhi consistently
Seems there's no relationship with Magnum service at all, you may need
to fix figure out why you can not access your test machine.
As for as I know, bay-create won't block your network access.
- Eli.
On 2016年08月11日 16:13, Yasemin DEMİRAL (BİLGEM BTE) wrote:
Hi
I installed magnum on
Hongbin & team
Please forget Semantic Versioning API, that should not be done in short
term especially API WG had defined lots
of Microversion API docs, sorry to make confusions.
Of cause that Microversion API is important to OpenStack, and it has
documented well in API WG [1].
For Magnum, I
Does anyone know that Magnum is a brand of ice cream[1]?
I love it! can we use it, maybe it may bring some copyright issue, but I
don't know..
[1] http://www.magnumicecream.com/us/en/home.html
On 2016年07月27日 13:47, hie...@vn.fujitsu.com wrote:
Hi all,
I think Magnum mascot should be
I am +1
Eli.
On 2016年07月23日 04:27, Hongbin Lu wrote:
Hi all,
Spyros has consistently contributed to Magnum for a while. In my
opinion, what differentiate him from others is the significance of his
contribution, which adds concrete value to the project. For example,
the operator-oriented
On 2016年07月20日 00:35, Waines, Greg wrote:
Does MAGNUM automatically download all Glance Images of a particular
Container Format to the COE ?
No, Magnum will not do this.
Only the swarm docker image is download by Magnum.
In the above setup, which Glance Image does the ‘docker image’
hi Vikas,
thanks for you clarify, relied in lines.
On 2016年06月22日 14:36, Vikas Choudhary wrote:
Magnum:
1. Support to pass neutron network names at container creation apis
such as pod-create in k8s case.
Hmm. Magnum has deleted all wrapper API for container creation and
pod-create
oh, so old of Juno, Kilo's reached EOL already.
Suggest you to add [sahara] in subject.
On 2016年06月03日 09:51, 阮鹏飞 wrote:
Hi, Friends,
I used Openstack-Juno heat, keystone and Mitaka sahara in CentOS7.
Sahara is installed in docker container using host network.
When sahara wants to call
s regex is still not tested, but regex update will work, this or
that way)
I will update this for swift soon in devstack after discussing with
swift team.
So, you can continue with higgins- as service name.
Please let me know in case I missed, something else, you wanted to point.
Best Regards,
hi team,
I am working on adding devstack plugin for Higgins, meet some troubles.
I named the service name as higgins-api, higgins-cond. in the plugin,
but I found that devstack try to install swift service,
and I got the reason is that [1], swift plugin try to grep 's-' in the
service name,
hi Tom
I like your idea on define a generic approach of bay life cycle operations.
Seems current propose is to allow user dynamically adding/deleting nodes
from a created bay, what if the master/node flavor in baymodel(bay's
flavor) ? if a user add a new node with flavor which is not defined
+1 for #2, to keep help message in magnum API server, since we have an
validation list in API Server, see
https://review.openstack.org/#/c/312990/5/magnum/api/attr_validator.py@23 .
But, if we chose #2 , CLI should add supporting to retrieve help message
from API server.
On 2016年05月12日
Thanks Matt
That really surprised me.
On 2016年05月03日 17:42, Matthew Booth wrote:
On Fri, Apr 29, 2016 at 2:47 AM, Eli Qiao > wrote:
hi team,
Is there any require that all compute node's instance_dir should
be same?
Yes. This
hi Timofei
I don't have any specific use case, this issue is found while I am doing
live migration testing, what I did is:
1. create 2 compute node,
2. create a nfs service on one of compute node, let's say node-2 and
expose /opt/stack/date/nova/instances
3. mount
+1,
Looking forward for reviewing this cool feature.
On 2016年04月21日 14:57, Kai Qiang Wu wrote:
Hi Duan Li,
We welcome to that contribution if you had. Just make sure that spec
can be flexible handle 2 ~ N flavor cases. That could handle future
requirements for N flavors, as in the ML, I
hi hello again
I believe you are talking about this bp
https://blueprints.launchpad.net/magnum/+spec/cache-docker-images
then ignore my previous reply, that may another topic to solve network
limited problem.
I think you are on the right way to build docker images but this image
could only
hi hongbin & team.
Thanks for all your supporting, Magnum core team and the community, I am
very glad to have this opportunity
to join this team. I will try my best to contribute Magnum team and
OpenStack community.
Thanks
Eli.
On 2016年04月08日 03:35, Hongbin Lu wrote:
Hi all,
Thanks for
20 matches
Mail list logo