Open Stack

Dear all,
Unfortunately, we could not attend the Design Summit. We also need some time 
before opening our source codes, mostly for our internal process. We will try
to shorten this time.

However, I finally got the approval from our boss and VP to make our projects
public yesterday, so we could start introduction to the OpenStack community.

On Sep, 24, seeing Eoghan Glynn's comment in this mailing list, we thought 
that the Synaps exactly fits the following descriptions.
> However, since metrics collection & alarming have much wider
> applicability than their use within orchestration, would it
> make sense to go one step further and hive off the CW/CWA-
> related logic into a completely separate infrastructure that
> could be independently deployed and be developed in parallel
> with the Heat project?
That's the reason we introduce Synaps before finishing the internal process.

Synaps implements the same CloudWatch APIs and we think that it can support 
any project which needs collection of metrics and alarms including Heat.
We're using Synaps for our auto scaling implementation in our private cloud.

Now we're preparing the overview of our project and other documentation.
If you have any questions, feel free to ask them at any time.

Here are answers of June Yi for Steven Hardy's questions below.
> - Is the metric collection secure/authenticated?
> - Are metrics collected from the hypervisors or in-instance?
> - Can service monitoring (in instance) metrics be collected?
> - Is the API authenticated (ie via keystone ec2 credentials?)

All metrics are collected using the API. The API is authenticated via auth 
module came from Nova.Authenticate WSGI middleware which supports AWS 
signature v2. It works well with LdapDriver. But we did not tested if it is 
working with keystone yet.

Default metrics (i.e. CPUUtilization, disk IO, network IO) are collected 
from hypervisors. Custom metrics can be collected from in-instance or 
any other source.

Regards,
--
Joonwon Lee, principal software engineer, Samsung SDS


------- Original Message -------
Sender : Eoghan Glynn<eglynn at redhat.com>
Date : 2012-10-10 18:59 (GMT+09:00)
Title : Re: [openstack-dev] Introducing Synaps project that provides AWS CloudWatch compatible API



> > > I'm working for Synaps project that provides AWS CloudWatch
> > > compatible API at Samsung SDS.
> > > Currently, we have plan to open the project to the community.
> > > 
> > > Here I introduce Synaps project:
> > > http://wiki.openstack.org/Synaps
> > 
> > Details are a bit scarce but at first glance there seem to be an
> > overlap
> > with the CloudWatch work in the Heat project ?
> 
> There certainly seems to be from the description, but pretty hard to
> evaluate until we see some code ;)

Yes, I would second that.

Once the code is out the open, the community will be much better placed
to judge which approach will make sense to concentrate efforts on.

June Yi - are you planning on attending the design summit?

Cheers,
Eoghan


> > Any chance the two groups could meet at the Design Summit next week
> > and
> > make sure we don't duplicate effort here ?
> > 
> > Angus Saskeld has a session on CloudWatch in the Incubation room:
> > http://openstacksummitfall2012.sched.org/event/60b0bcf1253efcb3dd72dff531d59d26
> 
> Angus Salkeld and Steve Dake will be at the Summit and could discuss,
> also
> possible overlap with metric collection in ceilometer (has been
> discussed
> previously).
> 
> I have several questions which will be make/break for the heat usage
> of
> Cloudwatch:
> 
> - Is the metric collection secure/authenticated?
> - Are metrics collected from the hypervisors or in-instance?
> - Can service monitoring (in instance) metrics be collected?
> - Is the API authenticated (ie via keystone ec2 credentials?)
> 
> Many more questions, need to see code and evaluate if we could use
> this for
> heat or if we continue with our own implementation.
> 
> --
> Steve Hardy
> Red Hat Engineering, Cloud
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev