Dears,
Attached files are introduction for this activity (in PDF and DOCX version) .
Below is the brief agenda in case the attachments are blocked:
Date: May 22nd, 2012
Location：China World Hotel, Beijing, China
Timeframe:
9:30-12:00 - General CloudStack Architecture
12:00-13:00 - Lun
+Anthony
I think we should not put the secondary storage in the host table since we do
not create an agent for it and do not send command to it. Since we do not
create an agent for it which connects with MS, the state remains in Alert and
means nothing.
I think the introduction of multiple seco
Just to add to it I had raised another UI bug
http://bugs.cloudstack.org/browse/CS-12626 to provide a way to display SSVM
agent's status since there
is no way on the UI to find out whether the SSVM agent is up and running
fine/disconnected or in Alert state and one has to go to the DB and find
> -Original Message-
> From: Nitin Mehta [mailto:nitin.me...@citrix.com]
> Sent: Monday, May 07, 2012 7:57 AM
> To: cloudstack-dev@incubator.apache.org; Ram Chinta
> Cc: David Nalley; Anthony Xu
> Subject: RE: Secondary nfs server alert issue
>
> Just to add to it I had raised another UI
Dear podling,
This email was sent by an automated system on behalf of the Apache Incubator
PMC.
It is an initial reminder to give you plenty of time to prepare your quarterly
board report.
The board meeting is scheduled for Wed, 16 May 2012, 10:00:00 PST. The report
for your podling will form
In 2.1.*, CloudStack only have one secondary storage and one SSVM for a zone,
so CloudStack uses one host entry to represent both. In 2.2.*, CloudStack
support multiple secondary storages and SSVMs, secondary storage status is not
used, but the entries are still being referred. Ideally, SSVM sho
>
> On May 4, 2012, at 8:37 AM, David Nalley wrote:
> > On Fri, May 4, 2012 at 12:24 AM, John Kinsella wrote:
> >> Guys - during the developer on-ramp this week, we held a group
> discussion around the topics of reviewing patch submissions, code
> maintainers, voting, and overall care and managem
On May 4, 2012, at 11:41 AM, David Nalley wrote:
> On Fri, May 4, 2012 at 2:38 AM, David Nalley wrote:
>> This is the first, of what I expect to be two drops of information.
>>
>> Edison still owes some code (he's supposedly going to put this on the wiki)
>>
>> Alena indicates that the code fr
On Fri, May 4, 2012 at 9:52 AM, Robert Schweikert wrote:
> On 05/04/2012 12:24 AM, John Kinsella wrote:
>>
>> Guys - during the developer on-ramp this week, we held a group discussion
>> around the topics of reviewing patch submissions, code maintainers, voting,
>> and overall care and management
On May 7, 2012, at 11:06 AM, Frank Zhang wrote:
>>
>> On May 4, 2012, at 8:37 AM, David Nalley wrote:
>>> On Fri, May 4, 2012 at 12:24 AM, John Kinsella wrote:
Guys - during the developer on-ramp this week, we held a group
>> discussion around the topics of reviewing patch submissions, cod
I realized that even in our mailing list, all the mail go through one
domain(incubator.apache.org), and you’re unable to “replay to all”. I
think this would very likely result in lost tracking of a certain
thread – for a big mailing list, you cannot go through all the mails
all day, so depends on t
On Mon, May 7, 2012 at 2:13 AM, 北川 大輔 wrote:
> Hi All!
>
> I still have problem I had a while ago...
>
>> Right after putting primary host to maintenance mode, all vm forced stop.
>> You would find it in a log files.
>
> Do anyone have same problem putting KVM to maintenance mode?
>
> Thank you
On 08/05/2012, at 4:24 AM, Sheng Yang wrote:
> I realized that even in our mailing list, all the mail go through one
> domain(incubator.apache.org), and you’re unable to “replay to all”. I
> think this would very likely result in lost tracking of a certain
> thread – for a big mailing list, you ca
>> - No top-quoting, only bottom quoting or in-line
I agree with most of these guidelines. I can see most of them makes sense for
plain text reading in emails/archives and on phones. The only one I have a
problem with is bottom-quoting. With most email clients supporting threading
nowadays,
+1
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Monday, May 07, 2012 4:44 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: E-Mail client guidelines on the mailing list
>
> >> - No top-quoting, only bottom quoting or in-line
>
> I agree with mo
On 5/7/12 4:51 PM, "Kelven Yang" wrote:
>+1
>
>> -Original Message-
>> From: Alex Huang [mailto:alex.hu...@citrix.com]
>> Sent: Monday, May 07, 2012 4:44 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: RE: E-Mail client guidelines on the mailing list
>>
>> >> - No top-quoting,
+1
On May 7, 2012, at 4:43 PM, Alex Huang wrote:
>>> - No top-quoting, only bottom quoting or in-line
>
> I agree with most of these guidelines. I can see most of them makes sense
> for plain text reading in emails/archives and on phones. The only one I have
> a problem with is bottom-quoting
+1
-Original Message-
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: Monday, May 07, 2012 4:44 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: E-Mail client guidelines on the mailing list
>> - No top-quoting, only bottom quoting or in-line
I agree with most of these guide
+1
-Original Message-
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: Monday, May 07, 2012 4:44 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: E-Mail client guidelines on the mailing list
>> - No top-quoting, only bottom quoting or in-line
I agree with most of these guide
+1
--
Ross Dakin
rossda...@gmail.com
(858) 699-2190
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Monday, May 07, 2012 4:44 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: E-Mail client guidelines on the mailing list
>
> >> - No top-quoting,
+1
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Monday, May 07, 2012 4:44 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: E-Mail client guidelines on the mailing list
>
> >> - No top-quoting, only bottom quoting or in-line
>
> I agree with mo
++
On 5/7/12 4:43 PM, "Alex Huang" wrote:
>>> - No top-quoting, only bottom quoting or in-line
>
>I agree with most of these guidelines. I can see most of them makes
>sense for plain text reading in emails/archives and on phones. The only
>one I have a problem with is bottom-quoting. With mos
+1
-Original Message-
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: Monday, May 07, 2012 4:44 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: E-Mail client guidelines on the mailing list
>> - No top-quoting, only bottom quoting or in-line
I agree with most of these guide
+1
>-Original Message-
>From: Fang Wang [mailto:fang.w...@citrix.com]
>Sent: Tuesday, May 08, 2012 6:04 AM
>To: cloudstack-dev@incubator.apache.org
>Subject: RE: E-Mail client guidelines on the mailing list
>
>+1
>
>-Original Message-
>From: Alex Huang [mailto:alex.hu...@citrix.com
Hello, Yang, Sheng!
> The fix would be in 3.0.2 release.
Thank you for informing this bug fix!
--
Daisuke kitagawa
Intelligence Business Solutions
1-4-4 Yanagibashi Taito-ku
Tokyo-to Japan 111-0052
Phone: +81 3 6385 6103
FAX: +81 3 6385 6104
http://ibs.inte.co.jp/
-Original Message--
+1
> -Original Message-
> From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
> Sent: Tuesday, May 08, 2012 7:09 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: E-Mail client guidelines on the mailing list
>
> +1
>
> >-Original Message-
> >From: Fang Wang
This information is useful to whoever adds new cloudStack APIs.
Starting in 3.0 release, all new APIs (except for list* ones) have to be
added as async. It is done to avoid situations we had in the past - when
the command originally was sync, then due to diff reasons we changed it to
become async.
27 matches
Mail list logo
