[
https://issues.apache.org/jira/browse/VCL-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Young-Hyun Oh resolved VCL-590.
---
Resolution: Fixed
Assignee: Young-Hyun Oh
OpenStack Module will be included in VCL 2.4. If we need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Young,
If you feel like OpenStack support is working okay, would you mind marking
VCL-590 as resolved when you get a chance?
https://issues.apache.org/jira/browse/VCL-590
We can create a new JIRA issue for 2.5 if we improve on support of OpenStack.
[
https://issues.apache.org/jira/browse/VCL-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Kurth reopened VCL-590:
The JSON Perl module is not getting installed by install_perl_libs. It needs
to be added.
> Openstack Mod
[
https://issues.apache.org/jira/browse/VCL-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Peeler resolved VCL-590.
--
Resolution: Fixed
> Openstack Module
>
>
>
0602 from [~hyuni93] in branch 'vcl/trunk'
[ https://svn.apache.org/r1650602 ]
VCL-590 OpenStack Module
Add openstackcomputermap and openstackimagerevision tables
Insert openstack module into module table
Insert openstack OSinstalltype into OSinstalltype table
Insert openstack pro
0600 from [~hyuni93] in branch 'vcl/trunk'
[ https://svn.apache.org/r1650600 ]
VCL-590 OpenStack Module
Add openstackcomputermap and openstackimagerevision tables
Insert openstack module into module table
Insert openstack OSinstalltype into OSinstalltype table
Insert openstack pro
Dear all,
I would like to ask about trunk version of OpenStack provisioning module.
What are the necessary database tables for the module, and what is the schema
of those table?
Can I use floating ip?
I would like to request your assitance.
Many thanks,
Aaron Toth
VCL System Administrator
Fau
hat using
> hostname
> >> to
> >> > > > find
> >> > > > > > the openstack instance id is not working properly and also can
> >> > cause
> >> > > > the
> >> > > > > > problem you described. I've back to use the
> openstackC
; > > _terminate_os_instance to check whether the instance is
>> completely
>> > > > > deleted
>> > > > > > or not. Please take a look at it again and let me know if you
>> have
>> > > any
>> > > > > > concerns. Thank you.
>
> [email protected]>
> > > > > > wrote:
> > > > > >
> > > > > > > Sounds like good progress to me. One comment though, it looks
> > like
> > > > > > > _terminate_os_instance does the DELETE request, check
> > > > > > success and then sleeps for 30 seconds while the instance
> deletes.
> > > > > However,
> > > > > > I don't believe a successful response to the DELETE request
> > > guarantees
> > > > > the
> > >
could
> result
> > > in a
> > > > > situation where multiple instances with the same name exist which
> > could
> > > > > cause _get_os_instance_id to return the wrong ID since it filters
> the
> > > > > instances based on name and selec
gt; > > > situation where multiple instances with the same name exist which
>> could
>> > > > cause _get_os_instance_id to return the wrong ID since it filters the
>> > > > instances based on name and selects the first in the list.
>> > > >
>> &
> instances based on name and selects the first in the list.
> > > >
> > > > I think either returning to using openstackComputerMap or looping
> with
> > a
> > > > timeout until the instance is actually deleted would be better
> choices.
&
ter in VCL into an
> error
> > > state which would make it more obvious something has gone wrong, though
> > at
> > > the cost of potentially failing a user's reservation. As an added
> > > precaution It might also be worth having _get_os_instance_id fail
ially failing a user's reservation. As an added
> > precaution It might also be worth having _get_os_instance_id fail if
> > there's more than one instance in the response.
> >
> > Cameron
> >
> >
> > On Fri, Jul 18, 2014 at 9:25 AM, YOUNG OH
> w
> precaution It might also be worth having _get_os_instance_id fail if
> there's more than one instance in the response.
>
> Cameron
>
>
> On Fri, Jul 18, 2014 at 9:25 AM, YOUNG OH wrote:
>
> > Cameron,
> >
> > I hope you had a great time and we
be worth having _get_os_instance_id fail if
there's more than one instance in the response.
Cameron
On Fri, Jul 18, 2014 at 9:25 AM, YOUNG OH wrote:
> Cameron,
>
> I hope you had a great time and welcome back to work :-). And, yes, the
> OpenStack module with directly using OpenStack API
Cameron,
I hope you had a great time and welcome back to work :-). And, yes, the
OpenStack module with directly using OpenStack APIs can solve the concerns
we've discussed and it's more flexible to apply new version of OpenStack
APIs, if necessary. In the updated openstack module, I&
Sorry for the silence from my end, I realized I forgot to mention I was
going to be on vacation for the last week and a half. Anyways, it looks
like Young's updates have addressed the main concerns we were having with
regards to the command line client. Given the progress he's made we think
going a
Andy,
Thank you for your comments. I've tried to apply what you addressed and
committed my module again. This module finds all openstack information
using OpenStack APIs and database. Thank you.
Best regards,
Young-Hyun
On Wed, Jul 9, 2014 at 10:24 AM, Andy Kurth wrote:
> Thanks Young. Look
Thanks Young. Looks good! If I understand correctly, you are avoiding the
need to use the CLI or cpan module by interacting directly with OpenStack
via the REST API?
It looks like the only commands you're running on the management node are
"nova" and "qemu-img" in _get_flavor_type. Would it be
Hi All,
I've committed my OpenStack module that replaced OpenStack CLIs to
OpenStack Compute APIs v2. I've took a look at the details of OpenStack
Perl SDKs and referred some of their features to my module like how it
handles OpenStack Compute APIs. This update OpenStack modul
back to you.
>
> Regards,
> Chris
>
> -Original Message-
> From: Cameron Mann [mailto:[email protected]]
> Sent: Monday, June 30, 2014 3:13 PM
> To: [email protected]
> Subject: Re: OpenStack Module
>
> Chris,
>
> Do you (or anyone else for that m
. I'll try and assess the current
state of JSON output compliance and get back to you.
Regards,
Chris
-Original Message-
From: Cameron Mann [mailto:[email protected]]
Sent: Monday, June 30, 2014 3:13 PM
To: [email protected]
Subject: Re: OpenStack Module
Chris,
Do you (or
.
>
> Regards,
> Chris
>
>
> -Original Message-
> From: Cameron Mann [mailto:[email protected]]
> Sent: Wednesday, June 25, 2014 2:38 PM
> To: [email protected]
> Subject: Re: OpenStack Module
>
> Hi all,
>
> We had a call earlier today to discu
essage-
From: Cameron Mann [mailto:[email protected]]
Sent: Wednesday, June 25, 2014 2:38 PM
To: [email protected]
Subject: Re: OpenStack Module
Hi all,
We had a call earlier today to discuss which OpenStack module we should focus
our development efforts on and at this point a community decision is r
Hi all,
We had a call earlier today to discuss which OpenStack module we should
focus our development efforts on and at this point a community decision is
required. For reference, Young Oh's module is available in trunk and ours
is on GitHub (https://github.com/cybera/openstack-vcl-module)
I think we're all in agreement that removing dependencies on /etc/hosts is
an improvement. I'm working on this and should have the changes committed
this week.
To summarize the situation and changes, the backend code currently reads
/etc/hosts in order to determine the private IP address of a nod
ouse in RHEL 6.5.
> Openstack Module
>
>
> Key: VCL-590
> URL: https://issues.apache.org/jira/browse/VCL-590
> Project: VCL
> Issue Type: New Feature
> Components: database, vcld (backend)
hiur
> Openstack Module
>
>
> Key: VCL-590
> URL: https://issues.apache.org/jira/browse/VCL-590
> Project: VCL
> Issue Type: New Feature
> Components: database, vcld (backend)
gt;>> Young-Hyun
> >> >>> >>>
> >> >>> >>>
> >> >>> >>>
> >> >>> >>> On Mon, Jun 2, 2014 at 3:56 PM, Curtis
> >> wrote:
> >> >>> >>>
> >> >>&
other
>> >>> >>> methods of finding the private ip of an instance in multi-host
>> >>> openstack
>> >>> >>> environment. If you have any other suggestions, please let me know.
>> >>> >>>
>> >>> >&g
> >>> >>> environment. If you have any other suggestions, please let me know.
> >>> >>>
> >>> >>
> >>> >> I'm not too sure what to do. I'm hoping the Apache VCL core devs
> chime
> >>> in.
> >>&g
>
>>> >> As far as I can tell, Apache VCL needs DNS resolution to work, so
>>> >> simply adding the IP into the database isn't going to be enough.
>>> >>
>>> >> For the current Apache VCL + OpenStack multihost cloud installation
>&
o work, so
>> >> simply adding the IP into the database isn't going to be enough.
>> >>
>> >> For the current Apache VCL + OpenStack multihost cloud installation
>> >> I'm working on I'm just going to add a python script that queries
&
on to work, so
> >> simply adding the IP into the database isn't going to be enough.
> >>
> >> For the current Apache VCL + OpenStack multihost cloud installation
> >> I'm working on I'm just going to add a python script that queries
> &
osts every 20 or 30 seconds or something
>> like that.
>>
>> Thanks,
>> Curtis.
>>
>>> Thanks,
>>> Young-Hyun
>>>
>>>
>>>
>>> On Mon, Jun 2, 2014 at 3:56 PM, Curtis wrote:
>>>
>>>> On Mon, Jun 2,
> OpenStack and generates /etc/hosts every 20 or 30 seconds or something
> like that.
>
> Thanks,
> Curtis.
>
>> Thanks,
>> Young-Hyun
>>
>>
>>
>> On Mon, Jun 2, 2014 at 3:56 PM, Curtis wrote:
>>
>>> On Mon, Jun 2, 2014 at 12:4
python script that queries
OpenStack and generates /etc/hosts every 20 or 30 seconds or something
like that.
Thanks,
Curtis.
> Thanks,
> Young-Hyun
>
>
>
> On Mon, Jun 2, 2014 at 3:56 PM, Curtis wrote:
>
>> On Mon, Jun 2, 2014 at 12:45 PM, YOUNG OH wrote:
>> &
ld like to bring your attention again to discuss what OpenStack
> module
> > should include. I would like to discus two issues first.
> >
> > First, we know that using /etc/hosts to get the private ip of an instance
> > can be problematic. Specifically, Cameron (at Cybera) and
ello Sir,
I want to setup OpenStack with Red HAT which is supported by VCL. My
motive is to configure VCL in OpenStack. Would you please help to configure my
desired VCL. It will be a great honor for me if you provide necessity details
about VCL.
Regards,
Moshiur
> Openstack
HAT which is supported by VCL. My
motive is to configure VCL in OpenStack. Would you please help to configure my
desired VCL. It will be a great honor for me if you provide necessity details
about VCL.
Regards,
Moshiur
> Openstack Module
>
>
>
On Mon, Jun 2, 2014 at 12:45 PM, YOUNG OH wrote:
> Hi All,
>
> I would like to bring your attention again to discuss what OpenStack module
> should include. I would like to discus two issues first.
>
> First, we know that using /etc/hosts to get the private ip of an instance
&g
the latest OpenStack (Icehouse) in RHEL 6.x,
please refer to the following site.
http://openstack.redhat.com/Quickstart
In fact, I am in the middle of testing the openstack module in the OpenStack
Icehouse now. I would love to share my experience with you once I finish my
test. I think I can post
Hi All,
I would like to bring your attention again to discuss what OpenStack module
should include. I would like to discus two issues first.
First, we know that using /etc/hosts to get the private ip of an instance
can be problematic. Specifically, Cameron (at Cybera) and I had found that
there
Hi All,
I have tested my openstack module (
https://issues.apache.org/jira/browse/VCL-590) on the OpenStack Icehouse
(The ninth release of OpenStack, April 17, 2014) and I could provisioning a
Linux image through it.
The environment details are as follows:
1. Host Blade
:- CPU: Intel(R) Xeon(R
t. For anyone feeling adventurous these are the
most basic instructions:
1. Apply the NAT patch
(https://issues.apache.org/jira/browse/VCL-174tested on 2.3 and 2.3.1,
make sure to read the Google doc)
2. Follow the instructions in the readme in the Github repo for the
OpenStack module.
Cameron
O
>
>
> 2. We use the Try::Tiny module to handle exceptions since the version of
> Perl VCL 2.3 uses doesn't support the saner try/catch mechanisms available
> in newer releases, however this would add an additional dependency to VCL.
> Depending on the version of Perl VCL 2.4 is planning to use what
Hi All --
One other thing I wanted to mention, fairly minor, is that OpenStack has
flavors for instances, which for VCL mostly means virtual CPUs and memory
given to a virtual machine. Right now, at Cybera, we just have a default
flavor, and then an optional flavor in the openstack image map datab
Hi Cameron,
Thanks for provided details of the modifications you added in to make
the module work at your site. I don't see any issues with what you
mentioned. Number 3 isn't really a major issue and the VCL core code
can be modified to not use the /etc/hosts file for the openstack
provisioning m
Hi all,
At Cybera we've been running VCL on OpenStack in production for a little
over a year now using a modified version of Young Oh's module. We talked
with Aaron, Josh and Andy last week about getting our code contributed back
into VCL and there are a few points that would need to be addressed
3158 from [~hyuni93] in branch 'vcl/trunk'
[ https://svn.apache.org/r1563158 ]
VCL-590
Initial work for OpenStack
> Openstack Module
>
>
> Key: VCL-590
> URL: https://issues.apache.org/jira/browse/VCL-590
> Pr
[
https://issues.apache.org/jira/browse/VCL-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Thompson updated VCL-590:
--
Fix Version/s: 2.4
> Openstack Module
>
>
>
[
https://issues.apache.org/jira/browse/VCL-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Peeler updated VCL-590:
-
Summary: Openstack Module (was: Openstack Essex Module)
> Openstack Mod
Mark,
Currently OpenStack module only supports Nova APs but I am planning to add
Quantum APIs to it.
In addition, I have plan to add the baremetal provisioning capability to
the OpenStack module after releasing the OpenStack Havana, which might have
more supports for baremetal provisioning
Does the OpenStack module support Quantum or just Nova?
Mark
On Mon, Sep 23, 2013 at 7:48 PM, Young h Oh wrote:
> Cameron,
>
> Not at all. You just reminded me right time about this issue. I will spend
> some time for both this issue and adding the OpenStack perl SDKs in our
Cameron,
Not at all. You just reminded me right time about this issue. I will spend
some time for both this issue and adding the OpenStack perl SDKs in our
OpenStack module. Then VCL can support Nova APIs, euca2ool, and oscompute
(OpenStack Perl SDK) to use the OpenStack environment. I will
Thanks for the reply. I didn't realize Curtis had already brought this up,
so I apologize for being repetitive. Mainly we just wanted to make sure
we're correctly understanding how the OpenStack module and VCL are
interacting so we can be confident in any workarounds we use in th
hange the instance private IP but the OpenStack module
does not keep checking the database to update the private IP in the hosts
file. The inconsistency between the openstack and vcl cause such problems.
In fact, I haven't looked at the module recently but I will spend some time
to change the
Hi all,
We've been using Young Oh's OpenStack module and we've run into an
interesting bug/behaviour. Below I use virtual machine to refer to the
entry for the computer in VCL and instance for the actual virtual machine
running in OpenStack.
When the module terminates an OpenSt
61 matches
Mail list logo
