Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/637#issuecomment-126233316
Changes LGTM, since we are creating a separate bug for correctly handling
log levels.
@DaanHoogland I am not saying to remove the interrupted exceptions
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/637#issuecomment-126185823
Since all these ignore messages are logged at INFO level, it needs to be
ensured that logs are not getting filled up too soon. Also I see lot of
instances
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/626#discussion_r35628826
--- Diff: debian/rules ---
@@ -1,6 +1,6 @@
#!/usr/bin/make -f
# -*- makefile -*-
-VERSION := $(shell mvn
org.apache.maven.plugins:maven
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/626#discussion_r35620265
--- Diff: debian/rules ---
@@ -1,6 +1,6 @@
#!/usr/bin/make -f
# -*- makefile -*-
-VERSION := $(shell mvn
org.apache.maven.plugins:maven
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/624#issuecomment-125470801
Already merged, looks like bot is not closing PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user koushik-das closed the pull request at:
https://github.com/apache/cloudstack/pull/624
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/607#issuecomment-125573161
@DaanHoogland I will create a separate test file with new the test case for
now. Once the issues in test_browse_templates.py are fixed, will merge it back
later
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/607#issuecomment-125849581
Moved the test to a new file test_browse_templates2.py. This is the command
to run it
nosetests-2.7 --with-marvin --marvin-config=setup/dev/advanced.cfg
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/624
Unit tests for HA manager investigate method. Refer to CLOUDSTACK-866â¦
â¦6 for the code chenges
You can merge this pull request into a Git repository by running:
$ git pull https
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/621#issuecomment-125156829
@wilderrodrigues Agree that refactoring the code might help with the tests.
But that will be a bigger effort.
---
If your project is set up for it, you can
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/607#issuecomment-125157246
@DaanHoogland Are you running some private simulator test? If so is it done?
---
If your project is set up for it, you can reply to this email and have your
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/621#issuecomment-125152445
@DaanHoogland Writing an unit test for changes in AgentManagerImpl.java is
hard due to the way the method gets invoked. Let me know if you have any
suggestion
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/607#issuecomment-125091277
Need one more LGTM. Anyone?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/621#issuecomment-124357139
Merging it as 2 LGTMs
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/622#issuecomment-124484710
lgtm
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/609#discussion_r35292541
--- Diff:
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/ADLdapUserManagerImpl.java
---
@@ -0,0 +1,81 @@
+/*
+ * Licensed
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/609#discussion_r35292477
--- Diff:
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/ADLdapUserManagerImpl.java
---
@@ -0,0 +1,81 @@
+/*
+ * Licensed
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/609#discussion_r35292608
--- Diff:
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/LdapManagerImpl.java
---
@@ -57,17 +57,22 @@
private
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/621
CLOUDSTACK-8666: Put host in Alert state only after alert.wait timeout
Instead of putting the host to Alert state immediately, the investigators
should be allowed to run for some time based
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/609#discussion_r35293493
--- Diff:
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/LdapUserManagerFactory.java
---
@@ -0,0 +1,55 @@
+/*
+ * Licensed
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/609#discussion_r35293652
--- Diff:
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/OpenLdapUserManagerImpl.java
---
@@ -0,0 +1,233 @@
+// Licensed
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/609#discussion_r35293580
--- Diff:
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/LdapUserManagerFactory.java
---
@@ -0,0 +1,55 @@
+/*
+ * Licensed
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/609#issuecomment-123998336
Once the comments are addressed, LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/607#discussion_r35300288
--- Diff: test/integration/component/test_browse_templates.py ---
@@ -1674,6 +1674,42 @@ def
-1 to dropping pre-4.x upgrade code. If possible we should suppress the old
upgrade files from coverity scan.
Reasons:
There may be users on pre-4.x versions.
Removing a functionality should be associated with proper documentation and an
advanced notification in some prior releases. This is
+1
On 22-Jul-2015, at 2:44 PM, Kishan Kavala kishan.kav...@citrix.com wrote:
I would like to add CoreOS as a supported OS type to cloudstack.
CoreOS vms can be created even now by selecting OS type as Other. There are
cloud providers supporting CoreOS offerings in production already.
By
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/609#discussion_r35291585
--- Diff:
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/ADLdapUserManagerImpl.java
---
@@ -0,0 +1,81 @@
+/*
+ * Licensed
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/609#discussion_r35291227
--- Diff:
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/LdapConfiguration.java
---
@@ -36,6 +36,8 @@
private static
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/610#issuecomment-123272585
@DaanHoogland Thanks for the information.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/611#issuecomment-123227873
Test browser based incomplete volume upload, followed by SSVM destroy.
Volume should go to UploadAbandoned/Error state and get cleaned up. ... ===
TestName
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/611
CLOUDSTACK-8655: [Browser Based Upload Volume] Partially uploaded volâ¦
â¦umes are not getting destroyed as part of storage GC
As part of volume sync, that runs during of SSVM
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/610#issuecomment-123232196
Changes look good. Not sure what dead local store mean.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/607
CLOUDSTACK-8651: [Browser Based Upload Template] Partially uploaded tâ¦
â¦emplates doesn't get cleaned up after the SSVM handling it is destroyed
Fixed template sync code
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/607#issuecomment-122836717
Test browser based incomplete template upload, followed by SSVM destroy.
Template should go to UploadAbandoned state and get cleaned up. ... ===
TestName
been ignored.
IMO, a PR siting for 7 or more days without a reply to the reviewer’s
questions/concerns should be closed without merge. In case it’s
really needed, the author will give it some attention and reopen it.
Cheers,
Wilder
On 14 Jul 2015, at 14:23, Koushik Das koushik
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/599#discussion_r34873680
--- Diff: framework/db/src/com/cloud/utils/db/Merovingian2.java ---
@@ -63,9 +63,7 @@
private Merovingian2(long msId) {
super
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/600#discussion_r34867930
--- Diff:
framework/ipc/src/org/apache/cloudstack/framework/serializer/OnwireClassRegistry.java
---
@@ -108,7 +107,7 @@ public void scan
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/600#issuecomment-15132
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/599#discussion_r34870126
--- Diff: framework/db/src/com/cloud/utils/db/Merovingian2.java ---
@@ -63,9 +63,7 @@
private Merovingian2(long msId) {
super
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/599#issuecomment-122242828
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user koushik-das commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/599#discussion_r34877501
--- Diff: framework/db/src/com/cloud/utils/db/Merovingian2.java ---
@@ -63,9 +63,7 @@
private Merovingian2(long msId) {
super
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/584#issuecomment-121183714
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
For bug fixes I feel 1 LGTM should be fine provided there is a Jira ticket with
all details and the request is pending for more than a specified time (may be 7
days). For new features the existing process should be fine.
-Original Message-
From: Wido den Hollander
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/571#issuecomment-120903118
@karuturi @DaanHoogland Added unit tests for CPVM allocation.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/573#issuecomment-121137019
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/571#issuecomment-121133952
Although RAT build status is showing ABORTED, the report is clean. Also the
build failed due to some random test failure. Since travis is green, I am going
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/578#issuecomment-121138178
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/571#issuecomment-121138730
Manually closing PR. I did a rebase to do away with unnecessary merge
commit.
---
If your project is set up for it, you can reply to this email and have your
Github user koushik-das closed the pull request at:
https://github.com/apache/cloudstack/pull/571
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/571
CLOUDSTACK-8623: CPVM fails to start after MS is restarted during itsâ¦
⦠initial start-up process
If SSVM cannot be started then the existing entry is removed and a new SSVM
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/557#issuecomment-118248923
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/553
CLOUDSTACK-8606: DB performance impacted due to VM sync.
VM sync. generates a lot of queries on vm_instance table with
'instance_name' as filter. Since the field is not
indexed
Congrats Karen!
-Original Message-
From: John Burwell [mailto:john.burw...@shapeblue.com]
Sent: Thursday, 2 July 2015 23:45
To: dev@cloudstack.apache.org
Cc: Karen Vuong
Subject: [ANNOUNCE] Karen Voung as a new PMC member of CloudStack
All,
The Project Management Committee (PMC) for
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/551
CLOUDSTACK-8603: Random list VM failures at scale (more than 1000 VMsâ¦
â¦) when VM has resource tags
There is no 'removed' field on the resource_tags table. So 'id' based
search
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/550
GitHub master
Patch for CLOUDSTACK-8603. Refer to the bug for details.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/koushik-das
I like the concept of quota. But I am thinking whether this should be a core
part of CS or developed as a plugin. Cloud coins example given below may be a
plugin, based on which decision to allow/disallow operation is made. Another
plugin could be to allow/disallow operations based on VM count
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/550#issuecomment-117765057
Discarding this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user koushik-das closed the pull request at:
https://github.com/apache/cloudstack/pull/550
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
On 01-Jul-2015, at 4:44 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
On 01-Jul-2015, at 12:31 pm, Koushik Das koushik@citrix.com wrote:
I like the concept of quota. But I am thinking whether this should be a core
part of CS or developed as a plugin.
It will be a separate
Congrats Wilder!
-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
Sent: Wednesday, 1 July 2015 22:43
To: dev
Subject: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack
The Project Management Committee (PMC) for Apache CloudStack are pleased to
Agree to what Funs mentioned. The current network service model is flexible,
there is option to select a provider for a given service by means of network
offering.
About using 3rd party VR, there are 2 possibilities:
- Fully replace the existing VR with 3rd party VR
- Both co-exist and
From the persistent config changes, it appears that aggregate command approach
is not required in 4.6 and onwards. If someone wants to implement the aggregate
approach only for 4.4 and 4.5 irrespective of the effort involved then that
should be fine.
Otherwise we can just put some config to
This is expected in a clustered MS setup. What is the distribution of HV hosts
across these MS (check host table in db for MS id)? MS owning the HV host
processes all commands for that host.
Grep for the sequence numbers (for e.g. 73-7374644389819187201) in both MS logs
to correlate.
On
?
On 04-Jun-2015, at 5:28 PM, Daan Hoogland daan.hoogl...@gmail.com wrote:
On Thu, Jun 4, 2015 at 1:27 PM, Koushik Das koushik@citrix.com wrote:
Is there a possibility for VR config and DB config to go out of sync? If so
how is the config in the VR and DB kept in sync?
Koushik, the db
Ian,
With the persistent config change, the VR has become 'stateful'.
Is there a possibility for VR config and DB config to go out of sync? If so how
is the config in the VR and DB kept in sync?
-Original Message-
From: Ian Southam [mailto:isout...@schubergphilis.com]
Sent: Thursday, 4
the regression in xen, i'm afraid
Op wo 3 jun. 2015 om 14:38 schreef Koushik Das koushik@citrix.com:
I think as a design principle we shouldn't introduce HV specific
checks in the orchestration/API layers.
I am not sure if the problem is specific to Vmware. Any out of band VR
movement can lead
at). Great it
is available in 4.4 as well so we can fix it in both 4.4 and 4.5 in the same
way.
On 03 Jun 2015, at 14:38, Koushik Das koushik@citrix.com wrote:
I think as a design principle we shouldn't introduce HV specific checks in
the orchestration/API layers.
I am not sure
In case the VR is moved out of band (say as part of Vmware DRS), all network
rules are lost. Rebooting VR from CS re-applies all the rules. Either the
reboot is done manually from UI/API or automatically as was done as part of
CLOUDSTACK-7994.
I haven't looked at the aggregate command. If it
limit the fix to this hypervisor only.
Regards,
Remi
On 03 Jun 2015, at 14:12, Koushik Das
koushik@citrix.commailto:koushik@citrix.com wrote:
In case the VR is moved out of band (say as part of Vmware DRS), all network
rules are lost. Rebooting VR from CS re-applies all the rules. Either
was not on the dev ML so I could not
reply
I reported this current behavior to be an issue on the user ML and wanted to
ask Koushik Das about his experiences.
I would not agree, in an Vmware environment live migrations, e.g. Vmware DRS
breaks IPtables normally. In my opinion, this would make DRS
On 04-Jun-2015, at 12:04 AM, Remi Bergsma rberg...@schubergphilis.com wrote:
Hi all,
I just had a look at this more closely and had a chat with Ian about it. The
only way for the original problem to happen (losing iptables rules) is if the
live migrate would fail and the hypervisor
I feel that the ACS docs needs to include clear/detailed steps for building
system VM templates. That way anyone can build templates from the source commit
a particular release is voted against.
-Koushik
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent:
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/263
Cloudstack-8301
PR for configuring local storage for system VMs at zone level.
FS @
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enable+configuring+local+storage+use
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/253#issuecomment-102248563
Added to CLOUDSTACK-8301 branch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
The below is the proposal for switching to XenServer HA.
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201403.mbox/%3c83f77ff1bd50194ab65afa5479d082a71e4...@sjcpex01cl02.citrite.net%3E
On 04-May-2015, at 9:03 PM, Tim Mackey tmac...@gmail.com wrote:
Thanks for starting this thread
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/222#issuecomment-98589348
I think there is agreement that this is a partial fix (with the right
intent). And that this PR doesn't add any value from the end-users perspective
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/222#issuecomment-98374391
@DaanHoogland It is not only to prevent NPE but also to go to the next item
in the list when the status cannot be determined. Think of it like this -
status
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/222#issuecomment-98372263
I thought the intent of introducing 'Unkonwn' host status was to replace
the entire null semantics that was thought to be confusing in the
investigators
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/222#issuecomment-98181315
@bhaisaab The 'null' semantics of all investigators needs to change to
'Unknown'. Just look at all classes that implements Investigator interface.
(XS, KVM
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/222#issuecomment-98183123
Also callers for investigate()/isAgentAlive() methods needs to be fixed to
handle Unknown instead of null.
---
If your project is set up for it, you can reply
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/211#issuecomment-98100569
One possible solution I can think of the original problem for this PR is to
wait for sometime (say based on the config parameter alert.wait) and if even
after
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/211#issuecomment-98100363
I looked at the code and saw that if investigate() is not able to determine
the state of host then by default Alert is returned, earlier it was null. This
may
Hi Daan,
In the slow build report mails, is it possible to add the findbug failures at
the top along with the commit ids?
-Koushik
-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
Sent: Friday, 1 May 2015 14:31
To: dev@cloudstack.apache.org
Subject: FW:
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/211#issuecomment-98120238
@remibergsma Yes XS (6.5) pool HA was enabled.
@DaanHoogland Agree on the new state UNKNOWN
---
If your project is set up for it, you can reply
Congrats Remi!
On 01-May-2015, at 12:15 PM, Daan Hoogland daan.hoogl...@gmail.com wrote:
The Project Management Committee (PMC) for Apache CloudStack
has asked Remi Bergsma to become a committer and we are pleased to
announce that he has accepted.
Remi has reported and helped in
Agree. The commit message should provide a summary of the changes.
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Wednesday, 29 April 2015 17:07
To: dev
Subject: Re: git commit: updated refs/heads/master to 07c3089
On Wed, Apr 29, 2015 at 5:45 AM,
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/211#issuecomment-97503915
@remibergsma My comments are based on the latest master code. Based on my
reading of the code, the changes you made shouldn't have any impact on the
outcome
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/211#issuecomment-97454863
@DaanHoogland If you look at the code from where testIpAddress() is called
(for e.g. UserVmDomRInvestigator.isAgentAlive()), it only deals with return of
Up
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/211#issuecomment-97452036
Reading the code, if testIpAddress() returns anything other than Up, Down
or null then returned status is ignored.
---
If your project is set up for it, you
Agree. I don't think it's possible currently. The listUsageRecords needs to be
modified.
-Original Message-
From: Ramzi Youssefi [mailto:ryouss...@gmail.com]
Sent: Wednesday, 15 April 2015 13:28
To: dev
Subject: listUsageRecord only for Admins? Why?
Hello developers!
is there any
Congrats Funs!
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Tuesday, 14 April 2015 1:12
To: dev
Subject: [ANNOUNCE] New committer: Funs Kessen
The Project Management Committee (PMC) for Apache CloudStack has asked Funs
Kessen to become a committer and
Congrats Gaurav!
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Tuesday, 14 April 2015 1:14
To: dev
Subject: [ANNOUNCE] New committer: Gaurav Nandkumar Aradhye
The Project Management Committee (PMC) for Apache CloudStack has asked Gaurav
Aradhya to become
+1
-Koushik
On 05-Apr-2015, at 2:44 PM, Ian Duffy i...@ianduffy.ie wrote:
Hi All,
As stated in a previous thread [1], myself, Sebastien and Darren are
proposing the donation of ec2stack [2].
I would like to call a vote, so that we have formal consensus on
accepting the code into the
After you have run deployDataCenter.py, it is possible to do VM/volume/network
related operations from UI.
From: Jeronimo Garcia [mailto:garciaj...@gmail.com]
Sent: Tuesday, 7 April 2015 17:25
To: dev@cloudstack.apache.org
Cc: cloudstack-...@incubator.apache.org
Subject: Re: Simulator.
One
Congrats Pierre-Yves!
-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: Wednesday, 1 April 2015 2:41
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] New committer Pierre-Yves Ritschard
The Project Management Committee (PMC) for Apache CloudStack has asked
Pierre-Yves
Congrats Rene!
-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: Wednesday, 1 April 2015 2:43
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] New committer: Rene Moser
The Project Management Committee (PMC) for Apache CloudStack has asked Rene
Moser to become a
Congrats Rohit!
-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com]
Sent: Friday, 27 March 2015 13:38
To: dev@cloudstack.apache.org
Subject: [ANNOUNCE] Rohit Yadav as new PMC member of CloudStack
The Project Management Committee (PMC) for Apache CloudStack are pleased
Congrats Sebastien and thanks Hugo!
-Original Message-
From: Giles Sirett [mailto:giles.sir...@shapeblue.com]
Sent: Monday, 23 March 2015 17:11
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org;
market...@cloudstack.apache.org
Subject: [Announce] - New VP Apache Cloudstack
All
Congrats Karen!
On 20-Mar-2015, at 3:37 AM, Pierre-Luc Dion pd...@cloudops.com wrote:
The Project Management Committee (PMC) for Apache CloudStack
has asked Karen Vuong to become a committer and we are pleased to
announce that she have accepted.
Karen is doing a huge effort on promoting
This is another alternate https://coreos.com/using-coreos/containers/. CS needs
to support CoreOS.
-Original Message-
From: Diwas Joshi [mailto:dj.dij...@gmail.com]
Sent: Monday, 16 March 2015 2:53
To: dev@cloudstack.apache.org
Subject: [DISCUSS] Support Docker as a hypervisor in
501 - 600 of 872 matches
Mail list logo
