[
https://issues.apache.org/jira/browse/CLOUDSTACK-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492183#comment-13492183
]
Wido den Hollander commented on CLOUDSTACK-443:
---
That would indeed work,
[
https://issues.apache.org/jira/browse/CLOUDSTACK-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492201#comment-13492201
]
Murali Reddy commented on CLOUDSTACK-443:
-
If you see my initial comment, it s
[
https://issues.apache.org/jira/browse/CLOUDSTACK-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Battala reassigned CLOUDSTACK-443:
-
Assignee: Rajesh Battala (was: Murali Reddy)
> health monitoring for loa
[
https://issues.apache.org/jira/browse/CLOUDSTACK-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492266#comment-13492266
]
Wido den Hollander commented on CLOUDSTACK-443:
---
Yes, that seems sane in
Wido den Hollander created CLOUDSTACK-449:
-
Summary: Disk I/O polling for instances
Key: CLOUDSTACK-449
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-449
Project: CloudStack
I
Wido den Hollander created CLOUDSTACK-450:
-
Summary: Controlling System VMs should not happen through SSH
Key: CLOUDSTACK-450
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-450
Project:
Wido den Hollander created CLOUDSTACK-451:
-
Summary: System VMs shouldn't be just Debian based
Key: CLOUDSTACK-451
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-451
Project: CloudStack
Rohit:
I saw the below commit, and then this:
http://pypi.python.org/pypi/cloudmonkey/0.0.4
Is this a release of a portion of the CloudStack codebase? (This
wasn't in the 4.0.0-incubating release was it?)
Did I miss a discussion of the publication on list somewhere?
--David
On Tue, Nov 6, 2012
Wido den Hollander created CLOUDSTACK-452:
-
Summary: IPv6 support
Key: CLOUDSTACK-452
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-452
Project: CloudStack
Issue Type: New Fea
Hi David,
Yes, the cli is part of the codebase in master's tools/cli and license wise
compliant.
No, it was not part of 4.0 and was recently committed only last week to fix
this feature issue:
https://issues.apache.org/jira/browse/CLOUDSTACK-132
which was requested here too:
https://issues.apac
On 07-Nov-2012, at 4:50 PM, David Nalley wrote:
> Rohit:
>
> I saw the below commit, and then this:
>
> http://pypi.python.org/pypi/cloudmonkey/0.0.4
>
> Is this a release of a portion of the CloudStack codebase? (This
> wasn't in the 4.0.0-incubating release was it?)
> Did I miss a discussio
Awesome job, everyone. Sorry I've been quiet the last week or two - had a
family emergency that I'm catching up after. Didn't get a chance to vote, but
been running the last 4.0.0-i RC for a while now and it looks great!
John
On Nov 6, 2012, at 12:29 PM, Joe Brockmeier wrote:
> Just pushed o
Hi!
Will there be live streams or recordings of the talks?
Cheers,
Wolfram
David Nalley created CLOUDSTACK-453:
---
Summary: KVM plugin used in the management server - is also needed
by the KVM agent - we should split those accordingly
Key: CLOUDSTACK-453
URL: https://issues.apache.org/ji
This is awesome! Congratulations!!
Thanks
Kimi
2012/11/7 John Kinsella
> Awesome job, everyone. Sorry I've been quiet the last week or two - had a
> family emergency that I'm catching up after. Didn't get a chance to vote,
> but been running the last 4.0.0-i RC for a while now and it looks gr
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7923/#review13214
---
Ship it!
Ship It!
- Marcus Sorensen
On Nov. 7, 2012, 7:31 a.m., D
[
https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy McAnally updated CLOUDSTACK-448:
--
Attachment: ssvm_dmesg.txt
dmesg from defunct SSVM
> SSVM bootstra
[
https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy McAnally updated CLOUDSTACK-448:
--
Attachment: ssvm_console.txt
Defunct SSVM console output
> SSVM bo
[
https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy McAnally updated CLOUDSTACK-448:
--
Attachment: ssvm_cloud.log.txt
/var/log/cloud.log
> SSVM bootstrap
Wido den Hollander created CLOUDSTACK-454:
-
Summary: cloud-utils package conflicts with cloud-utils from Ubuntu
Key: CLOUDSTACK-454
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-454
Pro
[
https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy McAnally updated CLOUDSTACK-448:
--
Attachment: screenshot-1.jpg
Screen shot of correctly configured XenServer network
[
https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492379#comment-13492379
]
Randy McAnally commented on CLOUDSTACK-448:
---
root@systemvm:~# cat /proc/cmdl
[
https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy McAnally updated CLOUDSTACK-448:
--
Attachment: management-server.log.txt
Management server log during the host add and
On Mon, Nov 5, 2012, at 03:40 PM, David Nalley wrote:
> On Mon, Nov 5, 2012 at 12:58 PM, Joe Brockmeier wrote:
> > In another thread, I think we were discussing monthly releases for minor
> > releases. IMHO, that's a good schedule and we should try for a monthly
> > release rather than trying to d
Should we add a line to this commit message, where people can mark whether
this patch should be considered for the next bugfix release? Or is that all
handled/tracked through JIRA or some other means? I just thought it would
be nice for the guy maintaining a release to be able to eventually pull in
[
https://issues.apache.org/jira/browse/CLOUDSTACK-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492433#comment-13492433
]
Marcus Sorensen commented on CLOUDSTACK-450:
Could it be done in stages? F
[
https://issues.apache.org/jira/browse/CLOUDSTACK-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492435#comment-13492435
]
Marcus Sorensen commented on CLOUDSTACK-452:
+1. I almost want to say that
[
https://issues.apache.org/jira/browse/CLOUDSTACK-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492438#comment-13492438
]
Marcus Sorensen commented on CLOUDSTACK-451:
This would perhaps provide in
[
https://issues.apache.org/jira/browse/CLOUDSTACK-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492439#comment-13492439
]
Simon Weller commented on CLOUDSTACK-452:
-
I agree with Marcus on this one.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy McAnally updated CLOUDSTACK-448:
--
Attachment: ssvm_vm-param-list.txt
xe-param-list output for the SSVM
David Nalley created CLOUDSTACK-455:
---
Summary: Many files listed twice in the spec file
Key: CLOUDSTACK-455
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-455
Project: CloudStack
Iss
David Nalley created CLOUDSTACK-456:
---
Summary: License tag in SPEC isn't what RPM is expecting
Key: CLOUDSTACK-456
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-456
Project: CloudStack
[
https://issues.apache.org/jira/browse/CLOUDSTACK-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Nalley resolved CLOUDSTACK-456.
-
Resolution: Fixed
commit e6b539ad734a2a081a472717d6f13e9e6b0e6490
Author: David Nalle
Hey all,
Looks like we're without a quorum for the weekly meeting. I checked in
#cloudstack-meeting at 17:00 UTC and seemed to be the only person
attending.
I suspect the time change, yesterday's release, and folks being at
ApacheCon have all contributed to the fact nobody showed up... I'll loo
Again, forgive my ignorance if I don't understand how this works for all
storage types, but it seems that when a template is first used in a cluster
we copy the template to primary storage first and use that for all
subsequent. Should we add an enhancement to be able to tag templates that
should be
Marcus,
You can add a plugin for something like that. I'm sure you'll need to make
some adjustments in cloudstack code to handle this (particularly specifying the
storage pool the vm should be on) but we should largely keep the logic outside
of cloudstack code and put it in a template.
- The
I was under the assumption the meeting was at 10am PST
Sent from my iPhone
On Nov 7, 2012, at 9:13 AM, Joe Brockmeier wrote:
> Hey all,
>
> Looks like we're without a quorum for the weekly meeting. I checked in
> #cloudstack-meeting at 17:00 UTC and seemed to be the only person
> attending.
- CountOnly should have it's own API. Putting it as a parameter to the call
and have it completely change the semantics of the response doesn't make sense
to me.
- If we return a count with the list, I agree with what George suggested. The
count should actually be in the header. It's more met
Me2
-Original Message-
From: Kelceydamage@bbits [mailto:kel...@bbits.ca]
Sent: Wednesday, November 07, 2012 9:42 AM
To: cloudstack-dev@incubator.apache.org
Cc: CloudStack Developers
Subject: Re: Today's IRC meeting
I was under the assumption the meeting was at 10am PST
Sent from my iPho
[
https://issues.apache.org/jira/browse/CLOUDSTACK-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492541#comment-13492541
]
Ram Ganesh commented on CLOUDSTACK-443:
---
Wido,
What you are referring to with S
So - the meeting is, or has been, set at 17:00 UTC. When I sent out the
reminder this week, I pointed out that it'd be one hour earlier for
folks in the U.S. (possibly elsewhere) due to the time change.
17:00 UTC is always the same time, regardless of Daylight Savings Time.
On Wed, Nov 7, 2012,
I agree about using plugins in general.
As far as local caching, I'm not really asking about adding a feature so
much as modifying the behavior of an existing one. It seems cloudstack
already does this (at least from what I've seen) download template to
primary storage.
I now see where the issue
Rohit,
Can I get the CLI only without going through the whole source code maven
install? Is it part of any RPM?
Thanks
ilya
-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@citrix.com]
Sent: Monday, November 05, 2012 11:35 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re:
I'm not sure how (cherry picking, pull based on commit message) this will work,
but it's good idea to mark the commit with some tag with say branch so we
always commit on master?
(Bugfix-for or Branch: )
Branch: 4.0, master #(comma separated branch names).
Bug-id: CLOUDSTACK-xxx
This may be amb
Really I just want to make sure that a commit I make that I know needs to
be pushed into the next 4.0 bugfix release gets there. Since someone else
is in charge of maintaining 4.0 and merging bug fixes, I can't do it
myself, and I'm not really sure how it works now. For example, does that
maintaine
yes, I think I'd mentioned in the thread or somewhere. Just use pip or
easy_install (apt-get install python-setuptools on ubuntu, install python2.6 or
above and pip if you don't have it);
sudo pip install cloudmonkey
or sudo easy_install cloudmonkey
now start cloudmonkey:
$ cloudmonkey
...
Wi
Marcus,
To my mind, it does not seem appropriate for developers to be making release
decisions at commit time. Instead, it feels more appropriate to me that these
decisions are captured in a ticket that is referenced from the commit message.
This separation allows the PMO/release management t
On 11/7/12 9:52 AM, "Alex Huang" wrote:
>- CountOnly should have it's own API. Putting it as a parameter to the
>call and have it completely change the semantics of the response doesn't
>make sense to me.
Alex, if we add new API, how do we request count for different CS objects
based on the ob
I don't know either, let's ask our release manager? Chip, Alex?
Probably a lot of manual checking, it should a committer's responsibility to
make sure a patch he's committed gets to all necessary branches.
In case of release, they should inform the release manager, either via commit
tags or expl
That's great, I'm fine with that if I need to create a bug for everything
that I know needs to be fixed in the 4.0 branch for example. The
header/tag in the commit message may not be something we end up officially
relying on by any means, but would help me as someone who perhaps maintains
a specif
It is feasible, if purely from CloudStack API perspectives, following
steps may help you get there (I didn't really try it in CloudStack UI
though)
1) Create 2 physical networks, in each of these physical networks, add a
guest traffic label, label it to vSwitch2, also tag the physical network,
say
[
https://issues.apache.org/jira/browse/CLOUDSTACK-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492633#comment-13492633
]
Jason Bausewein commented on CLOUDSTACK-448:
I had a similar issue and wou
Hi all,
Meeting minutes below. Please let me know if there are any questions.
===
#cloudstack-meeting Meeting
===
Meeting started by jzb at 18:04:59 UTC. The full logs are available at:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloud
Marcus,
To me, it feels like you are hitting on the difference in audience between a
commit message and a ticket. A commit message describes a technical scope,
impact, and reasoning of a particular revision in the repository which is
geared, primarily, towards other developers to understand th
Thank you Kelven,
I'm trying this out now. I had a similar setup before, but the network
offerings would not show up in cloudstack UI, I will try through APIs next.
Regards
ilya
-Original Message-
From: Kelven Yang [mailto:kelven.y...@citrix.com]
Sent: Wednesday, November 07, 2012 2:21
[
https://issues.apache.org/jira/browse/CLOUDSTACK-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492742#comment-13492742
]
Chip Childers commented on CLOUDSTACK-454:
--
More generally, should we be nami
We'd better fire bugs on issues.apache.org/cloudstack, add a tag for each
maintenance release(e.g. the upcoming 4.0.1), then release manager assign the
bugs to each developer. It's the developer's responsibility to fix the bug on
each maintenance branch, and write proper commit message, like, "B
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7877/#review13232
---
Ship it!
Looks to apply and build. We might do with a pass on the co
Alex Huang created CLOUDSTACK-457:
-
Summary: Test
Key: CLOUDSTACK-457
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-457
Project: CloudStack
Issue Type: Sub-task
Reporter:
[
https://issues.apache.org/jira/browse/CLOUDSTACK-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang reassigned CLOUDSTACK-457:
-
Assignee: Alex Huang
> Test
>
>
> Key: CLOUDSTACK-457
>
We should remember that we didn't have Jira setup until very late into the 4.0
release. There were a lot of things that leaked through because of that.
We should make use of the Jira functionalities.
These steps can be performed by everyone.
- A bug is filed in issues.apache.org/cloudstack. Th
[
https://issues.apache.org/jira/browse/CLOUDSTACK-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang resolved CLOUDSTACK-457.
---
Resolution: Not A Problem
> Test
>
>
> Key: CLOUDSTACK-457
>
The site looks nice. One comment I have and it's the same I had on
cloudstack-meeting irc.
We should keep a top-level link that points the user to the features and
progress of the next release. We had plenty of questions during 4.0 from users
about the progress of the release and the features
Now that cloudstack.org is redirecting to the apache site, where are the
password reset utilities?
+1 semver
+1 on 4 months as the timing. My opinion is that the more releases we'll do,
the better we'll get at it.
--Alex
-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Tuesday, November 06, 2012 11:25 PM
To: cloudstack-dev@incubator.apache.org
Subject: R
>From a non-developer perspective, more releases shows a project is actively
>being worked-on/improved. We I'm looking at new projects to fill needs,
>that's definitely something I look at.
Thanks
On Nov 7, 2012, at 4:42 PM, Alex Huang wrote:
> +1 semver
>
> +1 on 4 months as the timing. M
So as of 4.0 systemvm's don't live on secondary storage? in 3.0.2
you'd install the systemvm's to the secondary storage...
On Wed, Oct 31, 2012 at 10:15 AM, Marcus Sorensen wrote:
> The cloud-agent runs on the hosts, and is responsible for
> starting/running both system vms and guest instances. A
Hey all,
Some of the press we've gotten (so far) on the CloudStack
4.0.0-incubating release:
- CloudStack makes first release from Apache incubator
http://www.h-online.com/open/news/item/CloudStack-makes-first-release-from-Apache-incubator-1745092.html
- CloudStack releases first code under Apa
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7804/#review13238
---
Ship it!
Looked over and applied patch. Applies cleanly, docs build.
On 08-Nov-2012, at 4:57 AM, Clayton Weise wrote:
> Now that cloudstack.org is redirecting to the apache site, where are the
> password reset utilities?
Yes, the old site is here now: buildacloud.org. But I don't see the download
section, Joe can we put the on buildaclo
Thank you Joe. I have changed the status to Submitted for both the patches.
From: Joe Brockmeier [mailto:nore...@reviews.apache.org] On Behalf Of Joe
Brockmeier
Sent: Thursday, November 08, 2012 10:47 AM
To: Chip Childers; Wido den Hollander; David Nalley; Jessica Tomechak
Cc: Radhika Puthiyetath
On 08-Nov-2012, at 5:52 AM, Caleb Call wrote:
> From a non-developer perspective, more releases shows a project is actively
> being worked-on/improved. We I'm looking at new projects to fill needs,
> that's definitely something I look at.
Yes, but if we ignore the frequently released browser
>From the documentation perspective
+1 for 4-6 months for major release, and 2-3 months for patch/maintenance
release
-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@citrix.com]
Sent: Thursday, November 08, 2012 10:53 AM
To: cloudstack-dev@incubator.apache.org
Cc: Alex
[
https://issues.apache.org/jira/browse/CLOUDSTACK-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Brockmeier closed CLOUDSTACK-403.
-
Resolution: Fixed
Fixed w/commit 35dcda2.
> Installation guide refer
[
https://issues.apache.org/jira/browse/CLOUDSTACK-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Brockmeier resolved CLOUDSTACK-444.
---
Resolution: Fixed
Radhika submitted a patch via Review Board (https://reviews.apa
They do, but there's also an iso that is mounted with various extra
software. It's a way of updating the system vm.
On Wed, Nov 7, 2012 at 9:03 PM, Bryan Whitehead wrote:
> So as of 4.0 systemvm's don't live on secondary storage? in 3.0.2
> you'd install the systemvm's to the secondary storage..
On Thu, Nov 08, 2012 at 10:46:34AM +0530, Rohit Yadav wrote:
>
> On 08-Nov-2012, at 4:57 AM, Clayton Weise wrote:
>
> Now that cloudstack.org is redirecting to the apache site, where are
> the password reset utilities?
I think they're in the source tree, yes?
>> Yes, the
77 matches
Mail list logo
