Hi Ramy,
Thanks for the suggestion but since I am not including the neutron project,
so downloading and including it will require any additional configuration
in devstack-gate or not?
On Sat, Jul 18, 2015 at 11:41 PM, Asselin, Ramy wrote:
> We ran into this issue as well. I never found the roo
Hi Neutron folk!
I'd like to give an update on and encourage wide review of my work on
a type of network that connects VMs through IP routing instead of
through bridging and tunneling at L2. I believe the core Neutron
pieces of this are now complete and ready for detailed review and
potential me
Thanks Jay.
Hongbin, yes, it will be a scheduling system, either swarm, k8s or mesos. I
just think bay isn't a must in this case, and we don't need nova to provision
BM hosts, which makes things more complicated imo.
Peng
-- Original --
From: "Jay Lau";
Da
Hi Jay,
My idea is that if someone wants an IaaS solution, go Nova+Cinder+Neutron. For
private CaaS solution, K8S/Mesos+Cinder+Neutron(libnetwork?)+Docker, for public
CaaS, go K8S/Mesos+Cinder+Neutron+Hyper.
By doing this, we could clearly deliver the message to the community and
market. Wha
Peng,
You are not the first to think this way, and it's one of the reasons we did not
integrate Containers with OpenStack in a meaningful way a full year earlier.
Please pay attention closely.
1) OpenStack's key influences care about two personas: 1.1) Cloud Operators
1.2) Cloud Consumers. If
Just the export I mentioned:
export DEVSTACK_GATE_NEUTRON=1
Devstack-gate scripts will do the right thing when it sees that set. You can
see plenty of examples here [1].
Ramy
[1]
http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/devstack-gate.yaml#n467
From: Abhish
Hi Ramy,
Thanks for the suggestion. One more thing I need to ask, as I have have
setup one more CI so is there any way that we can decide that only required
projects should get downloaded and installed during devstack installation
dynamically. As I see no such things that can be done to devstack-g
On 07/15/2015 03:27 PM, John Griffith wrote:
It's relatively limited right now I think, and part of the reason for
that is we've tried to ensure that the information that we put on tags
is subjective
I think you mean "objective" here, and throughout this, not
"subjective". We try as much as po
On Sat, Jul 18, 2015 at 08:39:23PM +0800, Sam Stoelinga wrote:
> +1 on Kevin Benton's comments.
> Ironic should have integration with switches where the switches are SDN
> compatible. The individual bare metal node should not care which vlan,
> vxlan or other translation is programmed at the switch
There are two ways that I know of to customize what services are run:
1. Setup your own feature matrix [1]
2. Override enabled services [2]
Option 2 is probably what you’re looking for.
[1]
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
Hi John ,
Thanks for pointing me to the right script.
I appreciate your help .
I tried running the script with the following command :
[root@HSM-Client bin]# python pkcs11-key-generation --library-path
{/usr/lib/libCryptoki2_64.so} --passphrase {test123} --slot-id 1 mkek
--length 32 --label 'a
Matt Riedemann wrote:
>
> I think we're good now, let the rechecks begin!
Thanks so much for driving this, Matt. Don't burn out working on
weekends on it, though :)
(yes I realize the irony of posting that on a Sunday)
--
Thierry Carrez (ttx)
__
On 07/16/2015 05:13 AM, Thierry Carrez wrote:
> anyone with a stake in the game and their cat will upvote or
> downvote for no reason
I think we are overloaded on skewed information already and I'm not in
support of a structure that would likely offer gamed information.
Thanks,
Anita.
__
Hi all,
I think we are missing a category for plugins. I was thinking to following
plugins
-TLS plugin related to security. For example everything related to tls
access to the dashboard/vnc and apis
-Plugin to deploy freezer with fuel in order to achieve abckup and restore
(on going)
-plugin to se
So this has come up a few times. My question is, does having one node
serving several backends really form multiple AZs? Not really, the c-vol
node becomes a single point of failure.
There might be value in moving the AZ setting into the per-backend
configurables, if it doesn't work there already,
Don't include the curly brackets on the script arguments. The documentation is
just using them to indicate that those are placeholders for real values.
John Vrbanac
From: Asha Seshagiri
Sent: Sunday, July 19, 2015 2:15 PM
To: OpenStack Development Mailing List (
On Jul 16, 2015, at 4:13 AM, Thierry Carrez wrote:
> I don't really like the idea of a popularity contest to define "HA" or
> "scales" -- anyone with a stake in the game and their cat will upvote or
> downvote for no reason. I prefer to define HA in clear terms and have
> some group maintain the
Currently random mock objects are created inside of spec files to make writing
unit tests easier. This approach works but has some drawback:
* mocks are not sharable between specs.
* mocks are usually too simple.
* mocks may not be consistent between spec files.
* mocks are not te
My thoughts:
I think we'd better check what google will do after such official
announcement. As community changes fast, and we'd really welcome someone to
contributing it consistently and actively.
Thanks
Best Wishes,
---
I'm currently in holidays but I could not resist to take some time and
reply.
On 07/18/2015 06:32 PM, Dmitry Borodaenko wrote:
> It has been 5 weeks since Emilien has asked Fuel developers to
> contribute more
> actively to Puppet OpenStack project [0]. We had a lively discussion on
> openstack-de
Hi Peng,
As @Adrian pointed it out:
My fist suggestion is to find a way to make a nova virt driver for Hyper,
which could allow it to be used with all of our current Bay types in
Magnum.
I remembered you or other guys in your company proposed one bp about nova
virt driver for Hyper. What's the
The nova guys propose move Hyper to Magnum but not Nova as Hyper cannot fit
into nova virt driver well.
As Hyper is now integrating with Kubernetes, I think that the integration
point may be creating a kubernetes hyper bay with ironic driver.
Thanks
2015-07-20 10:00 GMT+08:00 Kai Qiang Wu :
> H
Hi ,
Could anyone please check the bug below?
https://bugs.launchpad.net/neutron/+bug/1467791
This bug description:
When the created network contains one ipv4 subnet and an ipv6 subnet which
turned on slaac or stateless.
When I create a port use cmd like:
neutron port-create --fixed-ip subnet_id
It looks like that Nova team has no plan to accept either nova-docker driver or
nova-hyper. The focus of Nova is "Server-like" instance, not App-centric
container. That is fine. It's the best to let Nova be Nova, and build sth. else
for container. After all, different use cases, different needs,
Adrian,
Let's say someone creates a Hyper bay. The bay will be sth. like
BM+Hyper+Cinder+Neutron+k8s/mesos/swarm. This is exactly a mini HyperStack.
What nova does in this scenario is to provision the Hyper+BM hosts. Things like
LiveMigration, Multi-tenancy, Billing, VPC, Volume, etc., are han
As exciting as these emails are, I find them a bit unexciting. They don't
give me any context to let me know whether this was a one-off or if
something has been broken for a while.
Long term, having a dashboard (see https://review.openstack.org/#/c/192253/
for the spec) will help us get better vis
As discussed at the last meeting we'll cancel this week (blame it on travel for
the mid-cycle meetup).
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786
__
OpenStack Development Mailing List (
Adrian,
Let's say someone creates a Hyper bay. The bay will be sth. like
BM+Hyper+Cinder+Neutron+k8s/mesos/swarm. This is exactly a mini HyperStack.
What nova does in this scenario is to provision the Hyper+BM hosts. Things like
LiveMigration, Multi-tenancy, Billing, VPC, Volume, etc., are han
Hi, Jay, Adrian and Wu,
I have some problems with my mail server to reply Adrian's message. So let me
write here.
Let's say someone creates a Hyper bay. The bay will be sth. like
BM+Hyper+Cinder+Neutron+k8s/mesos/swarm. This is exactly a mini HyperStack.
What nova does in this scenario is to
I had some problem with my email server today, so you may see several identical
messages from me in the ML. Please ignore and sorry about that.
Peng
-- Original --
From: "Peng Zhao";
Date: Mon, Jul 20, 2015 11:41 AM
To: "OpenStack Development Mailing List (
Adrian,
Let's say someone creates a Hyper bay. The bay will be sth. like
BM+Hyper+Cinder+Neutron+k8s/mesos/swarm. This is exactly a mini HyperStack.
What nova does in this scenario is to provision the Hyper+BM hosts. Things like
LiveMigration, Multi-tenancy, Billing, etc., are handled by Hyper
Hi Asselin, Abhishek,
Thanks for the reply. :)
On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi & Tang,
Sorry I missed this thread. Let me know if you've resolved your issues.
My repo is undergoing migrations to reuse components in
openstack-infra/puppet-openstackci.
For single-use-n
Adrian,
Let's say someone creates a Hyper bay. The bay will be sth. like
BM+Hyper+Cinder+Neutron+k8s/mesos/swarm. This is exactly a mini HyperStack.
What nova does in this scenario is to provision the Hyper+BM hosts. Things like
LiveMigration, Multi-tenancy, Billing, VPC, Volume, etc., are han
This is ok for the services it will install, but how can we also restrict
the downloading of all the projects(i.e; downloading only required
projects) ?
On Sun, Jul 19, 2015 at 11:39 PM, Asselin, Ramy wrote:
> There are two ways that I know of to customize what services are run:
>
> 1. Se
Adrian,
Let's say someone creates a Hyper bay. The bay will be sth. like
BM+Hyper+Cinder+Neutron+k8s/mesos/swarm. This is exactly a mini HyperStack.
What nova does in this scenario is to provision the Hyper+BM hosts. Things like
LiveMigration, Multi-tenancy, Billing, VPC, Volume, etc., are han
On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi & Tang,
Sorry I missed this thread. Let me know if you've resolved your issues.
My repo is undergoing migrations to reuse components in
openstack-infra/puppet-openstackci.
For single-use-nodes, the file you need has been removed here [1]
Hi Tang,
On Mon, Jul 20, 2015 at 11:18 AM, Tang Chen wrote:
> Hi Asselin, Abhishek,
>
> Thanks for the reply. :)
>
>
> On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
>
> HI Abhi & Tang,
>
>
>
> Sorry I missed this thread. Let me know if you’ve resolved your issues.
>
>
>
> My repo is undergoin
Hi Abhishek,
On 07/20/2015 02:09 PM, Abhishek Shrivastava wrote:
..
Quite a nice explanation +1 for all the things you have done. Just one
more thing to ask, have you made your slave node static?
Not yet. And I haven't made my nodepool. :)
These are my next step.
But before I start
Thanks Duncan. I was thinking if we can use volume_type instead of
available_zone totally. I mean whatever you have, one or many c-vol node,
you can just use volume_type to schedule volume creation on different
backends without using AZs at all. I also think available_zone is useless
if there is o
Hi, all.
I write a unit test in devstack and runs all tests okay on my environment.
Why does Jenkins failed when I upload my patch into review? The patch is
https://review.openstack.org/#/c/199588/. The failed test was named
"neutron.tests.unit.plugins.embrane.test_embrane_neutron_plugin.Tes
Hi,
I'm working on bug 1466451, which is about the invalid configuration of
property "pci_passthrough_whitelist" in nova.
My proposal for fixing this issue is:
Before start nova-compute sevice, do a precheck against /etc/nova/nova.conf
file, if the value format of "pci_passthrough_whitelist" do
For writing a Jenkins Job you can refer "*dsvm-cinder-driver.yaml.sample*"
as a reference.
On Mon, Jul 20, 2015 at 12:04 PM, Tang Chen wrote:
> Hi Abhishek,
>
> On 07/20/2015 02:09 PM, Abhishek Shrivastava wrote:
>
> ..
>
>
>
> Quite a nice explanation +1 for all the things you have don
42 matches
Mail list logo
