Future of CloudStack VMware Support
Since CloudStack is moving towards an Apache project, does that mean its great compatibility with ESXi will begin to fade away in future releases because development will be focused solely on open source hypervisors? That is the reason I had to move away from using OpenStack and would hate for the same thing to happen to CloudStack. Kevin F. Sent from my phone
Re: Future of CloudStack VMware Support
On Tue, Apr 24, 2012 at 8:30 AM, Kevin wrote: > Since CloudStack is moving towards an Apache project, does that mean its > great compatibility with ESXi will begin to fade away in future releases > because development will be focused solely on open source hypervisors? > > That is the reason I had to move away from using OpenStack and would hate for > the same thing to happen to CloudStack. > > Kevin F. > > Sent from my phone Hi Kevin: So first a disclaimer - I speak only for myself. That out of the way, there are no plans to ditch VMware support. It will likely become a bit more onerous to install. (CloudStack uses the VMware SDK which is not available under an Apache-friendly license (but is gratis), and as we come into line with the licensing policies of the ASF I imagine this SDK will disappear and the end-user will have to install this on their own) But if you check out http://wiki.cloudstack.org you'll see a number of folks working on a number of VMware-specific enhancements like Distributed vSwitch. --David
Re: Future of CloudStack VMware Support
Cloudstack has been Hypervisor agnostic all along. We cannot think of cloudstack that is tied to a Hypervisor. The developer community is very vibrant and won't let that happen. I think your concerns are misplaced. -Abhi - Original Message - From: Kevin [mailto:spam4...@gmail.com] Sent: Tuesday, April 24, 2012 06:00 PM To: cloudstack-dev@incubator.apache.org Subject: Future of CloudStack VMware Support Since CloudStack is moving towards an Apache project, does that mean its great compatibility with ESXi will begin to fade away in future releases because development will be focused solely on open source hypervisors? That is the reason I had to move away from using OpenStack and would hate for the same thing to happen to CloudStack. Kevin F. Sent from my phone
Re: version confusion
Hi Frank, On 04/23/2012 06:16 PM, Frank Zhang wrote: Hi Robert: Do you know what's most common way for java project packaging under Linux? The packaging is really independent from building the code. The most common build tool used for Java application on Linux is Ant. We look forward to getting rid of waf for a long while, but not see an easy way. Using scripts with Ant to package RPM seems to not have much difference that waf, for waf is a sort of scripts as well. The build tool should no create the package. From your perspective you should focus on building the code. For the install step the build tool should respect the value of the DESTDIR variable. everything else concerning the packaging is in the spec file, for RPMS, and equivalent for .dbe packages. Once decouple the code build, i.e. the transition from .java to .jar, and the package build (where stuff ends up on the system), things become a lot easier. A Java app should be no different in this respect than a C/C++ app. In the C/C++ world make is the build tool of choice. Upstream projects do not include rules about how to build packages in their makefiles. Neither should your build mechanism, may it be WAF or Ant. HTH, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjsch...@suse.com rschw...@ca.ibm.com 781-464-8147
jar dependency question
Hi, Looking at the build mechanism there are some hard coded jar dependencies, such as "tomcat6-servlet-2.5-api.jar", "tomcat6-el-2.1-api-6.0.24.jar", "tomcat6-jsp-2.1-api-6.0.24.jar", for RHEL. On SLES the tomcat6 expression language (tomcat6-el) is not available. What ill effects are to be expected without this functionality? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjsch...@suse.com rschw...@ca.ibm.com 781-464-8147
More packaging questions
Hi, Sorry for continuing to flood the list with more questions about this. Do I understand it correctly that everything that is related to console-proxy should not be packaged? This would include the /usr/lib64/cloud/console-proxy directory as well as the symlinks in /usr/lib64/cloud/agent that point to nodes in /usr/lib64/cloud/console-proxy, correct? /usr/share/java/cloud-console-proxy.jar should therefore also not be packaged? In what packages should /usr/bin/cloud-daemonize live? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjsch...@suse.com rschw...@ca.ibm.com 781-464-8147
RE: More packaging questions
>> Do I understand it correctly that everything that is related to console-proxy should not be packaged? Yes, you are right, console proxy should not be packaged, at one time, console proxy is deployed along with KVM agent, and this is the legacy from that. This feature has been depreciated. Kelven -Original Message- From: Robert Schweikert [mailto:rjsch...@suse.com] Sent: Tuesday, April 24, 2012 10:14 AM To: cloudstack-dev@incubator.apache.org Subject: More packaging questions Hi, Sorry for continuing to flood the list with more questions about this. Do I understand it correctly that everything that is related to console-proxy should not be packaged? This would include the /usr/lib64/cloud/console-proxy directory as well as the symlinks in /usr/lib64/cloud/agent that point to nodes in /usr/lib64/cloud/console-proxy, correct? /usr/share/java/cloud-console-proxy.jar should therefore also not be packaged? In what packages should /usr/bin/cloud-daemonize live? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjsch...@suse.com rschw...@ca.ibm.com 781-464-8147
Re: [cloudstack-users] Customizing system VMs without breaking existing system VM's?
> The identity of the system vm template / virtual router template is > determined in VMTemplateDaoImpl.java > (findRoutingTemplate etc). I'll poke around this. Thanks for the pointer. > This is not the best way : especially in a multihypervisor zone, the > selection of the template becomes muddy. I'll be in a pure XenServer zone, so I don't think that will be an issue. > The other question is : why do you want a different template? Starting a > VR requires a whole bunch of coordination with the management server > (patching, probing port 3922 etc). There are many different reasons one might want alternative routing templates. Primarily, the one I'm going after is this: As far as I can tell, if using an advanced networking install, there isn't a way to directly allocate a public IP to an instance. The only want to get a public IP is to allocate one as part of an isolated network with NAT mapping. I'd prefer to *not* deal with this NAT mapping. My alternative is to make a custom systemVM where I can customize/add my needs. At the same time, I don't want to break existing applications that are perfectly suited to use the Advanced Router. Protocols like SIP and the associated RTP do not play well with NAT's (it can be done but it really complicates things). Other examples are customized load balancers, session tracking, etc where underlying NAT is very application specific. Having multiple layers of NAT and redirection is something I'd like to avoid. Another can of worms is debugging, oftentimes (especially dealing with external organizations) I need direct access to the public IP for a tcpdump of a session. Not having this is really annoying (maybe i'm just too new to cloudstack?). > Note: "domainrouter" is a legacy name from CloudStack 1.0 which supported > XenServer exclusively. In XS, the virtual machine instances are called > "domains", and a special domain, "domain 0" exists to help the hypervisor. > The "domain router" was conceptualized to assist the CloudStack much in > the same manner. Today we call it "system vm" or "virtual router". > > > On 4/23/12 5:02 PM, "Bryan Whitehead" wrote: > >>http://docs.cloudstack.org/Knowledge_Base/Customizing_system_VMs >> >>This guide looks like I need to hack up the system vm image that all >>the systems VM's use. I'd like to create a parallel systemVM, >>specifically I'd like to keep the "Advanced Router" as is and also >>build a separate Router "fooBarRouter". Is this possible? >> >>The API call createServiceOffering looks like it can only have 3 >>options, "domainrouter", "consoleproxy" and "secondarystoragevm" for >>systemvmtype. Assuming I pass "systemvmtype=domainrouter" and set >>"issystem=true" I don't see how I can associate a different template >>for "domainrouter". Is this something inherited from "domainid"? >>Example, can a domain have a different default template for >>domainrouter? >> >>Or would I just use a preconfigured ServiceOffering and then tweak >>createNetworkOffering in some way to know an "Advance Router" would >>really be an alternative systemVM/templateid? >> >>Any pointers would be appreciated. I'm also willing to do the work to >>add this kind of functionality into CloudStack. >> >>-Bryan >> >>-- >> >>Live Security Virtual Conference >>Exclusive live event will cover all the ways today's security and >>threat landscape has changed and how IT managers can respond. Discussions >>will include endpoint security, mobile security and the latest in malware >>threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>___ >>cloudstack-users mailing list >>cloudstack-us...@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/cloudstack-users > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > cloudstack-users mailing list > cloudstack-us...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cloudstack-users
[DISCUSS] proposal to select a mascot for Apache CloudStack while in Incubation
Now that CloudStack is an Apache incubation project, it feels like it should have a mascot to help establish its own unique identity, similar to the Hadoop elephant, Linux penguin and Tomcat um, cat. I’d like to propose we do this in a way that allows the community to solicit ideas of for the mascot, then to vote on the final winner from a list of candidates. The idea is pretty simple: a) Put out a “call for submissions” and ask community members [you] to reply with their thoughts on what “Cloudy” should look like, and why. For example, a submission might say “I would design Cloudy as two lightning bolts with a blue cloud behind them. This would represent the scalability and power of CloudStack to build real production clouds.” (Note that I’ve been referring to the mascot as “Cloudy”, but if people have better ideas for the name, they could suggest that as well.) b) Have an independent designer read all the inputs, and create a series of cool design options based on the community input. c)Put up a website where everyone can vote on the best option. I’d propose we do it as a tournament style bracket where the mascots face off against each other, with the winners moving on based on community votes until we have a final winner. I’ve talked with the Citrix team about this. They agree with the goal and are very supportive of making sure CloudStack looks and feels like a true Apache project, not a commercial Citrix product. They have even volunteered to fund the designer and website (these would not be done by Citrix employees or have any Citrix branding – they’re only offering to fund them to help the goal of Apache CloudStack establishing its own identity and doing so in a fun, engaging way.) The final decision, of course, would need to be ratified by the PPMC, so after the community votes, we can take a vote in the PPMC to ratify their selection. Would be a simple up or down vote to accept the entry with the most votes. Proposed timeline: · “Call for Submissions” to be sent out to cloudstack-dev as soon as the PPMC approves this proposal · Submissions would be due by the end of the month (April 30) · Give the independent designer a week to do the designs · Launch the voting website at the beginning of the following week (May 7) · Let the voting run for a couple of weeks, depending on how many options are in the brackets · After the voting is complete, put the winning mascot choice out to PPMC for up/down vote to ratify (mid-to-late May) Feels like this would be a fun and engaging way to begin establishing a unique identity for CloudStack that’s clearly and visually independent from Citrix, and do it in a fun, engaging way that involves the broader community. Time is short, but if we keep to the above timeline, we could get the voting site up and running before the Citrix Synergy conference, which I think would be good for community optics. If folks like the general idea, we could call for a PPMC vote to move forward quickly. Peder
Re: [DISCUSS] proposal to select a mascot for Apache CloudStack while in Incubation
Sounds good - less than a week for submissions (I'm presuming PPMC approval will take a day or two) seems tight...but if this goes the way paper submissions go, 80% of the submissions will be on the last day, anyways. Just need to make sure we get the word out to folks. John On Apr 24, 2012, at 12:09 PM, Peder Ulander wrote: > Now that CloudStack is an Apache incubation project, it feels like it > should have a mascot to help establish its own unique identity, similar to > the Hadoop elephant, Linux penguin and Tomcat um, cat. > > > > I’d like to propose we do this in a way that allows the community to > solicit ideas of for the mascot, then to vote on the final winner from a > list of candidates. The idea is pretty simple: > > > > a) Put out a “call for submissions” and ask community members [you] to > reply with their thoughts on what “Cloudy” should look like, and why. For > example, a submission might say “I would design Cloudy as two lightning > bolts with a blue cloud behind them. This would represent the scalability > and power of CloudStack to build real production clouds.” (Note that I’ve > been referring to the mascot as “Cloudy”, but if people have better ideas > for the name, they could suggest that as well.) > > > > b) Have an independent designer read all the inputs, and create a > series of cool design options based on the community input. > > > > c)Put up a website where everyone can vote on the best option. I’d > propose we do it as a tournament style bracket where the mascots face off > against each other, with the winners moving on based on community votes > until we have a final winner. > > > > I’ve talked with the Citrix team about this. They agree with the goal and > are very supportive of making sure CloudStack looks and feels like a true > Apache project, not a commercial Citrix product. They have even volunteered > to fund the designer and website (these would not be done by Citrix > employees or have any Citrix branding – they’re only offering to fund them > to help the goal of Apache CloudStack establishing its own identity and > doing so in a fun, engaging way.) > > > > The final decision, of course, would need to be ratified by the PPMC, so > after the community votes, we can take a vote in the PPMC to ratify their > selection. Would be a simple up or down vote to accept the entry with the > most votes. > > > > Proposed timeline: > > > > · “Call for Submissions” to be sent out to cloudstack-dev as soon > as the PPMC approves this proposal > > · Submissions would be due by the end of the month (April 30) > > · Give the independent designer a week to do the designs > > · Launch the voting website at the beginning of the following week > (May 7) > > · Let the voting run for a couple of weeks, depending on how many > options are in the brackets > > · After the voting is complete, put the winning mascot choice out > to PPMC for up/down vote to ratify (mid-to-late May) > > > > Feels like this would be a fun and engaging way to begin establishing a > unique identity for CloudStack that’s clearly and visually independent from > Citrix, and do it in a fun, engaging way that involves the broader > community. Time is short, but if we keep to the above timeline, we could > get the voting site up and running before the Citrix Synergy conference, > which I think would be good for community optics. If folks like the general > idea, we could call for a PPMC vote to move forward quickly. > > > > Peder Stratosec - Secure Infrastructure as a Service o: 415.315.9385 @johnlkinsella
Re: [DISCUSS] proposal to select a mascot for Apache CloudStack while in Incubation
The ancient greeks had a "god" of the clouds and they called it Zeus. The roman counterpart is Jupiter. Haroon On 4/24/12 12:19 PM, "John Kinsella" wrote: >Sounds good - less than a week for submissions (I'm presuming PPMC >approval will take a day or two) seems tight...but if this goes the way >paper submissions go, 80% of the submissions will be on the last day, >anyways. Just need to make sure we get the word out to folks. > >John > >On Apr 24, 2012, at 12:09 PM, Peder Ulander wrote: > >> Now that CloudStack is an Apache incubation project, it feels like it >> should have a mascot to help establish its own unique identity, similar >>to >> the Hadoop elephant, Linux penguin and Tomcat um, cat. >> >> >> >> I¹d like to propose we do this in a way that allows the community to >> solicit ideas of for the mascot, then to vote on the final winner from a >> list of candidates. The idea is pretty simple: >> >> >> >> a) Put out a ³call for submissions² and ask community members >>[you] to >> reply with their thoughts on what ³Cloudy² should look like, and why. >>For >> example, a submission might say ³I would design Cloudy as two lightning >> bolts with a blue cloud behind them. This would represent the >>scalability >> and power of CloudStack to build real production clouds.² (Note that >>I¹ve >> been referring to the mascot as ³Cloudy², but if people have better >>ideas >> for the name, they could suggest that as well.) >> >> >> >> b) Have an independent designer read all the inputs, and create a >> series of cool design options based on the community input. >> >> >> >> c)Put up a website where everyone can vote on the best option. >>I¹d >> propose we do it as a tournament style bracket where the mascots face >>off >> against each other, with the winners moving on based on community votes >> until we have a final winner. >> >> >> >> I¹ve talked with the Citrix team about this. They agree with the goal >>and >> are very supportive of making sure CloudStack looks and feels like a >>true >> Apache project, not a commercial Citrix product. They have even >>volunteered >> to fund the designer and website (these would not be done by Citrix >> employees or have any Citrix branding they¹re only offering to fund >>them >> to help the goal of Apache CloudStack establishing its own identity and >> doing so in a fun, engaging way.) >> >> >> >> The final decision, of course, would need to be ratified by the PPMC, so >> after the community votes, we can take a vote in the PPMC to ratify >>their >> selection. Would be a simple up or down vote to accept the entry with >>the >> most votes. >> >> >> >> Proposed timeline: >> >> >> >> · ³Call for Submissions² to be sent out to cloudstack-dev as >>soon >> as the PPMC approves this proposal >> >> · Submissions would be due by the end of the month (April 30) >> >> · Give the independent designer a week to do the designs >> >> · Launch the voting website at the beginning of the following >>week >> (May 7) >> >> · Let the voting run for a couple of weeks, depending on how >>many >> options are in the brackets >> >> · After the voting is complete, put the winning mascot choice >>out >> to PPMC for up/down vote to ratify (mid-to-late May) >> >> >> >> Feels like this would be a fun and engaging way to begin establishing a >> unique identity for CloudStack that¹s clearly and visually independent >>from >> Citrix, and do it in a fun, engaging way that involves the broader >> community. Time is short, but if we keep to the above timeline, we could >> get the voting site up and running before the Citrix Synergy conference, >> which I think would be good for community optics. If folks like the >>general >> idea, we could call for a PPMC vote to move forward quickly. >> >> >> >> Peder > >Stratosec - Secure Infrastructure as a Service >o: 415.315.9385 >@johnlkinsella >
Re: [DISCUSS] proposal to select a mascot for Apache CloudStack while in Incubation
Another variant would be to open the submissions for a month or so and let those that want to submit their design ideas (actual images and artwork do so) as well as ideas. It let's people be creative and strut their stuff so to speak. Create a page on the CloudStack Incubator Wiki where people could post their ideas / submissions and then finalize them with a community vote (PPMC would ultimately be responsible for legal clearance and such). Tweet about it and let folks know its game on. Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine On Apr 24, 2012, at 3:19 PM, John Kinsella wrote: > Sounds good - less than a week for submissions (I'm presuming PPMC approval > will take a day or two) seems tight...but if this goes the way paper > submissions go, 80% of the submissions will be on the last day, anyways. Just > need to make sure we get the word out to folks. > > John > > On Apr 24, 2012, at 12:09 PM, Peder Ulander wrote: > >> Now that CloudStack is an Apache incubation project, it feels like it >> should have a mascot to help establish its own unique identity, similar to >> the Hadoop elephant, Linux penguin and Tomcat um, cat. >> >> >> >> I’d like to propose we do this in a way that allows the community to >> solicit ideas of for the mascot, then to vote on the final winner from a >> list of candidates. The idea is pretty simple: >> >> >> >> a) Put out a “call for submissions” and ask community members [you] to >> reply with their thoughts on what “Cloudy” should look like, and why. For >> example, a submission might say “I would design Cloudy as two lightning >> bolts with a blue cloud behind them. This would represent the scalability >> and power of CloudStack to build real production clouds.” (Note that I’ve >> been referring to the mascot as “Cloudy”, but if people have better ideas >> for the name, they could suggest that as well.) >> >> >> >> b) Have an independent designer read all the inputs, and create a >> series of cool design options based on the community input. >> >> >> >> c)Put up a website where everyone can vote on the best option. I’d >> propose we do it as a tournament style bracket where the mascots face off >> against each other, with the winners moving on based on community votes >> until we have a final winner. >> >> >> >> I’ve talked with the Citrix team about this. They agree with the goal and >> are very supportive of making sure CloudStack looks and feels like a true >> Apache project, not a commercial Citrix product. They have even volunteered >> to fund the designer and website (these would not be done by Citrix >> employees or have any Citrix branding – they’re only offering to fund them >> to help the goal of Apache CloudStack establishing its own identity and >> doing so in a fun, engaging way.) >> >> >> >> The final decision, of course, would need to be ratified by the PPMC, so >> after the community votes, we can take a vote in the PPMC to ratify their >> selection. Would be a simple up or down vote to accept the entry with the >> most votes. >> >> >> >> Proposed timeline: >> >> >> >> · “Call for Submissions” to be sent out to cloudstack-dev as soon >> as the PPMC approves this proposal >> >> · Submissions would be due by the end of the month (April 30) >> >> · Give the independent designer a week to do the designs >> >> · Launch the voting website at the beginning of the following week >> (May 7) >> >> · Let the voting run for a couple of weeks, depending on how many >> options are in the brackets >> >> · After the voting is complete, put the winning mascot choice out >> to PPMC for up/down vote to ratify (mid-to-late May) >> >> >> >> Feels like this would be a fun and engaging way to begin establishing a >> unique identity for CloudStack that’s clearly and visually independent from >> Citrix, and do it in a fun, engaging way that involves the broader >> community. Time is short, but if we keep to the above timeline, we could >> get the voting site up and running before the Citrix Synergy conference, >> which I think would be good for community optics. If folks like the general >> idea, we could call for a PPMC vote to move forward quickly. >> >> >> >> Peder > > Stratosec - Secure Infrastructure as a Service > o: 415.315.9385 > @johnlkinsella > signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [DISCUSS] proposal to select a mascot for Apache CloudStack while in Incubation
> · “Call for Submissions” to be sent out to cloudstack-dev as soon > as the PPMC approves this proposal Speaking only for myself - I don't think you need PPMC permission to move forward with this idea - I'd of course suggest ensuring a community consensus, making sure folks are well informed, etc. but otherwise, just go get things done. You shouldn't need to get approval and annointing to start getting things done IMO, especially when 'getting things done' means soliciting ideas on this list. Obviously final decisions around identity and trademarks have a legal component and that would be the responsibility of the PPMC.
RE: OVS tunnel manager feature merged in master and 3.0.x
Yes, definitely.
KVM support is already on the agenda and will be added soon.
Salvatore
> -Original Message-
> From: John Kinsella [mailto:j...@stratosec.co]
> Sent: 24 April 2012 03:04
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: OVS tunnel manager feature merged in master and 3.0.x
>
> Cool! I'm going to be on basic networking for a few months so not quite
> ready to try it, but will this eventually support KVM?
>
> John
>
> On Apr 23, 2012, at 6:08 PM, Salvatore Orlando wrote:
>
> > Hi,
> >
> > Just a quick heads-up to inform that the Open vSwitch tunnel manager is
> now available in Cloudstack's master and 3.0.x branches.
> > Chiradeep summarized the problem, and the solution, in a few slides:
> > http://www.slideshare.net/chiradeep_v/cloudstack-sdn
> >
> > A more complete (and possibly boring) description of the feature is
> described at
> http://wiki.cloudstack.org/display/RelOps/Open+vSwitch+tunnel+manager+
> for+Cloudstack; please not that it will be available as a "tech preview" for
> Bonita. A full-bodied implementation can be expected in upcoming releases.
> >
> >
> > - If you wish to give your feedback or suggesting ways for
> > improving
> the implementation, please feel free to live your comments on the
> 'improvements' page, available at
> http://confluence.cloudstack.org/display/RelOps/Open+vSwitch+tunnel+ma
> nager+improvements (it's a bit raw at the moment, but we will update it
> soon!)
> >
> > - If you want to try the feature, make sure your database is up-to-
> date. If you're currently running a db version < 3.0.3 then the upgrade script
> should kick in when the management server starts, upgrading the DB for you.
> > Otherwise, run the following SQL against the 'cloud' database:
> >
> > CREATE TABLE `cloud`.`ovs_tunnel_interface` (
> >
> > `id` bigint(20) NOT NULL AUTO_INCREMENT,
> >
> > `ip` varchar(16) DEFAULT NULL,
> >
> > `netmask` varchar(16) DEFAULT NULL,
> >
> > `mac` varchar(18) DEFAULT NULL,
> >
> > `host_id` bigint(20) DEFAULT NULL,
> >
> > `label` varchar(45) DEFAULT NULL,
> >
> > PRIMARY KEY (`id`)
> >
> > ) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=utf8;
> >
> >
> > INSERT INTO `cloud`.`ovs_tunnel_interface` (`ip`, `netmask`, `mac`,
> > `host_id`, `label`) VALUES ('0', '0', '0', 0, 'lock');
> >
> > CREATE TABLE `cloud`.`ovs_tunnel_network`( `id` bigint unsigned NOT
> > NULL UNIQUE AUTO_INCREMENT, `from` bigint unsigned COMMENT 'from
> host
> > id', `to` bigint unsigned COMMENT 'to host id', `network_id` bigint
> > unsigned COMMENT 'network identifier', `key` int unsigned COMMENT
> > 'gre key', `port_name` varchar(32) COMMENT 'in port on open vswitch',
> > `state` varchar(16) default 'FAILED' COMMENT 'result of tunnel
> > creatation', PRIMARY KEY(`from`, `to`, `account`)
> > ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
> >
> > INSERT INTO `cloud`.`ovs_tunnel_network` (`from`, `to`, `network_id`,
> > `key`, `port_name`, `state`) VALUES (0, 0, 0, 0, 'lock', 'SUCCESS');
> >
> > Finally, it is quite likely you'll find something which is not working
> > properly!
> If that is the case, please file an issue on jira.cloudstack.org and assign
> it to
> either me (Salvatore Orlando) or Chiradeep Vittal. Please also specify
> "Network Controller" as the affected component.
> >
> > Salvatore
> >
> >
>
> Stratosec - Secure Infrastructure as a Service
> o: 415.315.9385
> @johnlkinsella
Re: OVS tunnel manager feature merged in master and 3.0.x
Great.. we will start testing it next week and fill bugs if any.
On Mon, Apr 23, 2012 at 9:08 PM, Salvatore Orlando <
salvatore.orla...@eu.citrix.com> wrote:
> Hi,
>
> Just a quick heads-up to inform that the Open vSwitch tunnel manager is
> now available in Cloudstack's master and 3.0.x branches.
> Chiradeep summarized the problem, and the solution, in a few slides:
> http://www.slideshare.net/chiradeep_v/cloudstack-sdn
>
> A more complete (and possibly boring) description of the feature is
> described at
> http://wiki.cloudstack.org/display/RelOps/Open+vSwitch+tunnel+manager+for+Cloudstack;
> please not that it will be available as a "tech preview" for Bonita. A
> full-bodied implementation can be expected in upcoming releases.
>
>
> - If you wish to give your feedback or suggesting ways for
> improving the implementation, please feel free to live your comments on the
> 'improvements' page, available at
> http://confluence.cloudstack.org/display/RelOps/Open+vSwitch+tunnel+manager+improvements(it's
> a bit raw at the moment, but we will update it soon!)
>
> - If you want to try the feature, make sure your database is
> up-to-date. If you're currently running a db version < 3.0.3 then the
> upgrade script should kick in when the management server starts, upgrading
> the DB for you.
> Otherwise, run the following SQL against the 'cloud' database:
>
> CREATE TABLE `cloud`.`ovs_tunnel_interface` (
>
> `id` bigint(20) NOT NULL AUTO_INCREMENT,
>
> `ip` varchar(16) DEFAULT NULL,
>
> `netmask` varchar(16) DEFAULT NULL,
>
> `mac` varchar(18) DEFAULT NULL,
>
> `host_id` bigint(20) DEFAULT NULL,
>
> `label` varchar(45) DEFAULT NULL,
>
> PRIMARY KEY (`id`)
>
> ) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=utf8;
>
>
> INSERT INTO `cloud`.`ovs_tunnel_interface` (`ip`, `netmask`, `mac`,
> `host_id`, `label`) VALUES ('0', '0', '0', 0, 'lock');
>
> CREATE TABLE `cloud`.`ovs_tunnel_network`(
> `id` bigint unsigned NOT NULL UNIQUE AUTO_INCREMENT,
> `from` bigint unsigned COMMENT 'from host id',
> `to` bigint unsigned COMMENT 'to host id',
> `network_id` bigint unsigned COMMENT 'network identifier',
> `key` int unsigned COMMENT 'gre key',
> `port_name` varchar(32) COMMENT 'in port on open vswitch',
> `state` varchar(16) default 'FAILED' COMMENT 'result of tunnel
> creatation',
> PRIMARY KEY(`from`, `to`, `account`)
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>
> INSERT INTO `cloud`.`ovs_tunnel_network` (`from`, `to`, `network_id`,
> `key`, `port_name`, `state`) VALUES (0, 0, 0, 0, 'lock', 'SUCCESS');
>
> Finally, it is quite likely you'll find something which is not working
> properly! If that is the case, please file an issue on jira.cloudstack.organd
> assign it to either me (Salvatore Orlando) or Chiradeep Vittal. Please
> also specify "Network Controller" as the affected component.
>
> Salvatore
>
>
>
Re: .jar modification in Cloudstack
Thank you, It was actually related to different versions.. We saw that the 3.0.1 branch on github is actually getting updated still. so we had different versions. On Mon, Apr 23, 2012 at 4:06 PM, Chiradeep Vittal < chiradeep.vit...@citrix.com> wrote: > No, check the permissions. Tomcat runs as 'cloud' user and can probably > not load files with 'root' ownership > > On 4/23/12 12:51 PM, "David Chamard" wrote: > > >Hi, > > > >We are running into a problems trying to modify a jar in our > >beta environment while it was working fine in our dev environment running > >the same version (3.0.1) . We basically had to modify the cloud-server.jar > >to have the swift UI work and handles api keys. We replaced the > >cloud-server.jar with the new version on the "beta" server in > >/usr/share/java and in /usr/share/cloud/management/client/WEB-INF/lib but > >now the cloud-management server wont start. > > > >Is there any mechanics that checks for md5 or that validates .jar files? > > > >Thanks, > > > >David > >
Re: .jar modification in Cloudstack
On Tue, Apr 24, 2012 at 5:02 PM, David Chamard wrote: > Thank you, > > It was actually related to different versions.. We saw that the 3.0.1 > branch on github is actually getting updated still. so we had different > versions. > > If you want real 3.0.1 - use the 3.0.1 tag - if you are looking at what will be 3.0.2, I think that is what 3.0.1 branch is being used for atm. --David
Re: [DISCUSS] proposal to select a mascot for Apache CloudStack while in Incubation
David is right. The PPMC is really only there to make sure that Apache's interests and obligations are met. They do not really "Control" the project in as much as make sure things that need to be done (like filing reports, dealing with trademark, legal issues). A sign of a healthy community is communicate on the list and just do it. In this case, your advocating for a logo / mascot ... +1, great idea. At this point, the Citrix folks (no offense) really don't have a lot to do with it inasmuch as the Apache CloudStack product does. So, the only process at this point is see if anyone has an objection (so far it doesn't sound like it). I'd suggest making a Wiki page where people can post their ideas. Pick an end date, I suggest 30 days, post and wait. At the end of the 30-days take a community vote and the logo with the most votes wins :) When Citrix donated to the code to Apache and the community was formed it is the community that gets to decide the fate, good or bad, on its own Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine On Apr 24, 2012, at 4:49 PM, David Nalley wrote: >> · “Call for Submissions” to be sent out to cloudstack-dev as soon >> as the PPMC approves this proposal > > > Speaking only for myself - I don't think you need PPMC permission to > move forward with this idea - I'd of course suggest ensuring a > community consensus, making sure folks are well informed, etc. but > otherwise, just go get things done. You shouldn't need to get approval > and annointing to start getting things done IMO, especially when > 'getting things done' means soliciting ideas on this list. Obviously > final decisions around identity and trademarks have a legal component > and that would be the responsibility of the PPMC. signature.asc Description: Message signed with OpenPGP using GPGMail
Fw: [PATCH] - support SLES and openSUSE as configuration and build targets (#8)
-- Forwarded message -- From: Robert Schweikert Date: Tue, Apr 24, 2012 at 1:26 PM Subject: [CloudStack] - support SLES and openSUSE as configuration and build targets (#8) To: hudsoncloudies You can merge this Pull Request by running: git pull https://github.com/rjschwei/CloudStack suseBuild Or you can view, comment on it, or merge it online at: https://github.com/CloudStack/CloudStack/pull/8 -- Commit Summary -- * - support SLES and openSUSE as configuration and build targets -- File Changes -- A agent/distro/opensuse/sles/SYSCONFDIR/init.d/cloud-agent.in (141) A agent/distro/sles/SYSCONFDIR/init.d/cloud-agent.in (141) A client/distro/opensuse/SYSCONFDIR/init.d/cloud-management.in (234) A client/distro/opensuse/SYSCONFDIR/sysconfig/cloud-management.in (6) A client/distro/sles/SYSCONFDIR/init.d/cloud-management.in (234) A client/distro/sles/SYSCONFDIR/sysconfig/cloud-management.in (6) A python/distro/opensuse/SYSCONFDIR/init.d/cloud-ipallocator.in (101) A python/distro/sles/SYSCONFDIR/init.d/cloud-ipallocator.in (101) A usage/distro/opensuse/SYSCONFDIR/init.d/cloud-usage.in (96) A usage/distro/sles/SYSCONFDIR/init.d/cloud-usage.in (96) M wscript_configure (29) -- Patch Links -- https://github.com/CloudStack/CloudStack/pull/8.patch https://github.com/CloudStack/CloudStack/pull/8.diff --- Reply to this email directly or view it on GitHub: https://github.com/CloudStack/CloudStack/pull/8
Re: [DISCUSS] proposal to select a mascot for Apache CloudStack while in Incubation
+1 on both what David and Matt said On Tue, Apr 24, 2012 at 11:37 PM, Matt Hogstrom wrote: > David is right. The PPMC is really only there to make sure that Apache's > interests and obligations are met. They do not really "Control" the > project in as much as make sure things that need to be done (like filing > reports, dealing with trademark, legal issues). A sign of a healthy > community is communicate on the list and just do it. > > In this case, your advocating for a logo / mascot ... +1, great idea. > > At this point, the Citrix folks (no offense) really don't have a lot to do > with it inasmuch as the Apache CloudStack product does. So, the only > process at this point is see if anyone has an objection (so far it doesn't > sound like it). I'd suggest making a Wiki page where people can post their > ideas. Pick an end date, I suggest 30 days, post and wait. > > At the end of the 30-days take a community vote and the logo with the most > votes wins :) > > When Citrix donated to the code to Apache and the community was formed it > is the community that gets to decide the fate, good or bad, on its own > > Matt Hogstrom > m...@hogstrom.org > > A Day Without Nuclear Fusion Is a Day Without Sunshine > > On Apr 24, 2012, at 4:49 PM, David Nalley wrote: > > >> · “Call for Submissions” to be sent out to cloudstack-dev as > soon > >> as the PPMC approves this proposal > > > > > > Speaking only for myself - I don't think you need PPMC permission to > > move forward with this idea - I'd of course suggest ensuring a > > community consensus, making sure folks are well informed, etc. but > > otherwise, just go get things done. You shouldn't need to get approval > > and annointing to start getting things done IMO, especially when > > 'getting things done' means soliciting ideas on this list. Obviously > > final decisions around identity and trademarks have a legal component > > and that would be the responsibility of the PPMC. > > -- Thanks - Mohammad Nour "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein
Tree view refreshing in 3.0.1
Hi,
We use the "treeview (" the one in the domains section) for our object
store UI add-on and you absolutely need to close and reopen the "arrow" at
a top of a tree to be able to refresh the list. Is there a reason behind
this and is there a patch planned?
Thanks,
David
