Dear Valued Waines, Greg Customer:
Please advise payment actual date for this invoice.
Thank you for your valued custom.
Waines, Greg
Direct #: 836-338-6252
870-188-1601 x247
e greg.wai...@windriver.com
-
This email transmission is intended only for the use of the individual or
entity
k.org"
Subject: Re: [openstack-dev] [glance] Glance API Caching Enhancements for Edge
Computing
Hi Greg,
Have you actually filed a blueprint or specs for this in glance?
If yes could you please provide a reference for the same.
Thanks & Best Regards,
Abhishek Kekane
On Thu, Oct 4,
Glance Team,
I am following up on discussions in the edge-computing PTG meetings.
There were discussions on potential enhancements to Glance API Caching for
support of the proposed MVP Edge Architecture.
And I took the action to write up a blueprint and a specification for these
enhancements ...
e it to use
keystone for authentication. So keystone can't use Barbican for this. Chicken
and egg problem.
On 08/29/2018 08:08 PM, Waines, Greg wrote:
My understanding is that Keystone can be configured to use Barbican to securely
store user passwords.
Is this true ?
If yes, is this the standard /
My understanding is that Keystone can be configured to use Barbican to securely
store user passwords.
Is this true ?
If yes, is this the standard / recommended / upstream way to securely store
Keystone user passwords ?
If yes, I can’t find any descriptions of this is configured ?
Can someone pr
of the possible
architectures for image synchronisation
Hi,
Going inline.
From: Waines, Greg [mailto:greg.wai...@windriver.com]
Sent: Friday, June 29, 2018 4:25 AM
In-lined comments / questions below,
Greg.
From: "Csatari, Gergely (Nokia - HU/Budapest)"
mailto:gergely.csat...@nokia.
_and_multiple_Glance_API_servers
From: Csatari, Gergely (Nokia - HU/Budapest)
Sent: Monday, June 11, 2018 4:29 PM
To: Waines, Greg ; OpenStack Development Mailing
List (not for usage questions) ;
edge-comput...@lists.openstack.org
Subject: RE: [Edge-computing] [edge][glance][mixmatch]: Wi
Hey ... a couple of NEWBY question for the Barbican Team.
I just setup a devstack with Barbican @ stable/queens .
Ran through the “Verify operation” commands (
https://docs.openstack.org/barbican/latest/install/verify.html ) ... Everything
worked.
stack@barbican:~/devstack$ openstack secret li
ixmatch]: Wiki of the possible
architectures for image synchronisation
Hi,
Going inline.
From: Waines, Greg [mailto:greg.wai...@windriver.com]
Sent: Thursday, June 7, 2018 2:24 PM
I had some additional questions/comments on the Image Synchronization Options (
https://wiki.openstack.org/wiki/Imag
I had some additional questions/comments on the Image Synchronization Options (
https://wiki.openstack.org/wiki/Image_handling_in_edge_environment ):
One Glance with multiple backends
· In this scenario, are all Edge Clouds simply configured with the one
central glance for its GLANCE E
Re-posting this question to ‘OPENSTACK REFSTACK’,
Any guidance on what level of compliance is required to qualify for the
OpenStack Logo ( https://www.openstack.org/brand/interop/ ),
See questions below.
Greg.
From: Greg Waines
Date: Monday, February 26, 2018 at 6:22 PM
To: "openstack-dev@lists
week
?
Hi Greg,
We can meet near croke park hotel reception at 9:00am. Is it ok?
Regards
Tushar
________
From: Waines, Greg mailto:greg.wai...@windriver.com>>
Sent: Friday, March 2, 2018 1:45:37 AM
To: OpenStack Development Mailing List (not for usage qu
Greg,
We below are present:
Tushar Patil(tpatil)
Yukinori Sagara(sagara)
Abhishek Kekane(abhishekk)
Dinesh Bhor(Dinesh_Bhor)
Thank you,
Dinesh Bhor
From: Waines, Greg mailto:greg.wai...@windriver.com>>
Sent: 28 February 2018 19:22:26
To: OpenStack
Any masakari folks at the PTG this week ?
Would be interested in meeting up and chatting,
let me know,
Greg.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.or
· I have a commercial OpenStack product that I would like to claim
compliancy with RefStack
· Is it sufficient to claim compliance with only the “OpenStack Powered
Platform” TESTS ?
oi.e. https://refstack.openstack.org/#/guidelines
oi.e. the ~350-ish compute + object-stor
Any thoughts on this ?
Greg.
From: Greg Waines
Reply-To: "openstack-dev@lists.openstack.org"
Date: Friday, January 19, 2018 at 3:10 PM
To: "openstack-dev@lists.openstack.org"
Cc: "Nasir, Shoaib"
Subject: [openstack-dev] [magnum] [ironic] Why does magnum create instances
with ports using 'fix
Masakari Installation and
Procedure and/or Documentation
Hello Greg,
Thank you for reporting & researching.
On 2018/01/27 5:59, Waines, Greg wrote:
Update on this.
It turned out that i had incorrectly set the ‘project_name’ and ‘username’ in
/etc/masakarimonitors/masakarimonitors.conf
Sett
: Re: [openstack-dev] [masakari] BUG in Masakari Installation and
Procedure and/or Documentation
Hello Greg,
Thank you for reporting & researching.
On 2018/01/27 5:59, Waines, Greg wrote:
Update on this.
It turned out that i had incorrectly set the ‘project_name’ and ‘username’ in
Update on this.
It turned out that i had incorrectly set the ‘project_name’ and ‘username’ in
/etc/masakarimonitors/masakarimonitors.conf
Setting both these attributes to ‘admin’ made it such that the
instancemonitor’s notification to masakari-engine was successful.
e.g.
stack@devstack-masakar
I am looking for some input before I raise a BUG.
I reviewed the following commits which documented the Masakari and
MasakariMonitors Installation and Procedures.
i.e.
https://review.openstack.org/#/c/489570/
https://review.openstack.org/#/c/489095/
I created an AIO devstack with Masakari on cur
From reading the Masakari API Specifications commit
(https://review.openstack.org/#/c/512591/)
I believe that the proper syntax for the host and segment creates is as follows:
masakari segment-create --name segment-1 --recovery-method auto --service-type
COMPUTE
masakari host-create --name --t
masakari segment-create --name segment-1 --recovery-method auto --service-type
xyz
For ‘service-type’,
· what are the semantics of this parameter ?
· what are the allowed values ?
· what is a typical or example value ?
masakari host-create --name devstack-masakari -
Hey there,
We have just recently integrated MAGNUM into our OpenStack Distribution.
QUESTION:
When MAGNUM is creating the ‘instances’ for the COE master and minion nodes,
WHY does it create the instances with ports using ‘fixed-ips’ ?
- instead of just letting the instance’s port
Hey there,
I am currently running magnum with the fedora-atomic image that is installed as
part of the devstack installation of magnum.
This fedora-atomic image has kubernetes with a CRI of the standard docker
container.
Where can i find (or how do i build) a fedora-atomic image with kubernetes
"
Date: Thursday, December 7, 2017 at 12:24 AM
To: "openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [masakari] problems starting up masakari instance
monitoring in devstack @ master
Hello Greg,
I forgot to tell you.
Please use process_list.yaml instead of proc.
sakari instance
monitoring in devstack @ master
Hello Greg,
I forgot to tell you.
Please use process_list.yaml instead of proc.list.sample.
On 2017/12/07 14:03, Rikimaru Honjo wrote:
Hello Greg,
Please use masakarimonitors.conf instead of hostmonitor.conf and
processmonitor.conf.
You can ge
got to tell you.
Please use process_list.yaml instead of proc.list.sample.
On 2017/12/07 14:03, Rikimaru Honjo wrote:
Hello Greg,
Please use masakarimonitors.conf instead of hostmonitor.conf and
processmonitor.conf.
You can generate it by "tox -egenconfig".
hostmonitor.conf and processmonitor.conf are us
genconfig".
hostmonitor.conf and processmonitor.conf are used for monitors implemented by
shell script.
masakarimonitors.conf is a configuration file for monitors implemented by
python that you installed.
And, we are preparing setting guides.
Please see it if you are good.
masakari:
https://r
.conf are used for monitors implemented by
shell script.
masakarimonitors.conf is a configuration file for monitors implemented by
python that you installed.
And, we are preparing setting guides.
Please see it if you are good.
masakari:
https://review.openstack.org/#/c/489570/
masakari-monitor
plemented by
python that you installed.
And, we are preparing setting guides.
Please see it if you are good.
masakari:
https://review.openstack.org/#/c/489570/
masakari-monitors:
https://review.openstack.org/#/c/489095/
Best regards,
On 2017/12/06 22:48, Waines, Greg wrote:
I am just getting starte
od.
masakari:
https://review.openstack.org/#/c/489570/
masakari-monitors:
https://review.openstack.org/#/c/489095/
Best regards,
On 2017/12/06 22:48, Waines, Greg wrote:
I am just getting started working with masakari.
I am working on master.
I have setup Masakari in Devstack (see details at e
I am just getting started working with masakari.
I am working on master.
I have setup Masakari in Devstack (see details at end of email) ... which
starts up masakari-engine and masakari-api processes.
I have git cloned the masakari-monitors and started them up (roughly) following
the instructio
ist
I think that your second suggestion, of the vitrage_type and regex, could work
better. Is there any other reason to add the vitrage_alarm_type property, other
than for suppression purposes?
Best Regards,
Ifat.
From: "Waines, Greg"
Reply-To: "OpenStack Development Mailing
Thinking about this more ...
· Any thoughts on adding a ‘vitrage_alarm_type (enum or short string)’
as a mechanism to identify the general type of problem or alarm being reported
in order to address this ?
ocould be an optional field
obut we’d display in the alarm list
oand we
Hey,
I am interested in getting some feedback on a proposed blueprint for Vitrage.
BLUEPRINT:
TITLE: Add the ability to ‘suppress’ alarms by Alarm Type and/or Resource
When managing a cloud, there are situations where a particular alarm or a set
of alarms from a particular resource are occurri
ia IPMI/Redfish/SNMP/ssh) to manage
power state of its big brother.
The pxe_ssh driver is about libvirt VMs simulating bare-metal nodes. I
am not sure this is what you need. Also, pxe_ssh driver is obsoleted by
the virtualbmc proxy by now.
On 11/21/2017 05:22 PM, Waines, Greg wrote:
Hey,
We h
edocs.io/en/latest/README.html
[2] - https://pypi.python.org/pypi/virtualbmc/1.2.0
On Tue, Nov 21, 2017 at 5:22 PM, Waines, Greg
mailto:greg.wai...@windriver.com>> wrote:
Hey,
We have been integrating OpenStack Ironic into our own OpenStack Distribution.
Thanks to help from the mailing l
Hey,
We have been integrating OpenStack Ironic into our own OpenStack Distribution.
Thanks to help from the mailing list, we’ve been able to successfully ‘nova
boot’ a bare metal instance on an ironic node using the pxe_ipmitool drivers.
Thanks again for all the help.
A QUESTION about some futur
k-dev@lists.openstack.org"
Date: Thursday, November 16, 2017 at 2:59 PM
To: "openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [ceilometer] Blueprint proposals for 'file'
publisher: Compression and CSV file format
On 2017-11-16 02:48 PM, Waines, Greg wrote
k-dev@lists.openstack.org"
Date: Thursday, November 16, 2017 at 1:49 PM
To: "openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [ceilometer] Blueprint proposals for 'file'
publisher: Compression and CSV file format
On 2017-11-16 12:44 PM, Waines, Greg wrote:
Hey there,
I am looking for some feedback on 2x enhancement / blueprint proposals for the
‘file’ publisher in ceilometer.
i.e.
https://github.com/openstack/ceilometer/blob/master/ceilometer/publisher/file.py
Are the Ceilometer owners open to looking at blueprints for the following ?
1.
Is there a ‘current’ high-level description of the openstack masakari
architecture ?
I can only find these:
https://wiki.openstack.org/wiki/Masakari#Architecture
https://www.slideshare.net/masahito12/masakari-virtual-machine-high-availability-for-openstack
but i am pretty sure these are out-of-da
hould be good to go.
-jay
On 10/30/2017 01:05 PM, Waines, Greg wrote:
Hey,
We are in the process of integrating OpenStack Ironic into our own
OpenStack Distribution.
Still pulling all the pieces together ... have not yet got a successful
‘nova boot’ yet, so issues below could be configuration or s
Hey,
We are in the process of integrating OpenStack Ironic into our own OpenStack
Distribution.
Still pulling all the pieces together ... have not yet got a successful ‘nova
boot’ yet, so issues below could be configuration or setup issues.
We have ironic node enrolled ... and corresponding nov
Hey,
We are in the process of integrating OpenStack Ironic into our own OpenStack
Distribution.
Is there support for a single OpenStack system supporting VM and Baremetal
Instances simultaneously ? ( in NEWTON ? in PIKE ? )
I BELIEVE the answer is yes.
BUT can someone confirm ?
And then, if
Hey,
We are in the process of integrating OpenStack Ironic into our own OpenStack
Distribution.
One of the areas that we cannot find a good description of is:
How is the interface for the tftpboot server typically configured on OVS ?
i.e.
· i know tftpboot server runs on the same n
Is this a known issue in NEWTON ?
i.e. it does NOT appear that murano client uses the http_proxy environment
variable defined in /etc/environment
e.g. murano package-import
will NOT work behind a proxy server, even if http_proxy is
defined in /etc/environment
Is this fixed
copies of OVMF_VARS.fd ?
On 09/27/2017 09:09 AM, Waines, Greg wrote:
> Hey there ... a question about UEFI booting of VMs.
>
> i.e.
>
> glance image-create --file cloud-2730. qcow --disk-format qcow2
> --container-format bare --property “hw-firmware-type=uefi” --name
> clea
Any info on this ?
I did launch a VM with UEFI booting and did not see any copy of OVMF_VARS.fd
proactively copied into /etc/nova/instances// .
Maybe Nova only does that on a change to OVMF_VARS.fd ???
( haven’t figured out how to do that )
anyways any info or pointers would be appreciated,
than
Hey there ... a question about UEFI booting of VMs.
i.e.
glance image-create --file cloud-2730. qcow --disk-format qcow2
--container-format bare --property “hw-firmware-type=uefi” --name
clear-linux-image
in order to specify that you want to use UEFI (instead of BIOS) when booting
VMs with thi
Just another note on this ...
We have
· setup a ‘magnum’ domain, and
· setup a ‘trustee_domain_admin’ user within that domain, and
· gave that user and domain the admin role, and <-- actually not
100% sure about this
· referenced these items in magnum.conf
We are in the process of integrating MAGNUM into our OpenStack distribution.
We are working with NEWTON version of MAGNUM.
We have the MAGNUM processes up and running and configured.
However we are seeing the following error (see stack trace below) on virtually
all MAGNUM CLI calls.
The code whe
name:
- collectd_host: …
If this doesn’t help, please send me the file and I’ll have a look.
Best Regards,
Ifat.
From: "Waines, Greg"
Date: Tuesday, 5 September 2017 at 15:38
To: "Afek, Ifat (Nokia - IL/Kfar Sava)" , "OpenStack
Development Mailing List (no
notifications, not statistics.
Can you please turn on the debug option in /etc/vitrage/vitrage.conf (set
“debug = true”), and send me the vitrage-graph.log?
Thanks,
Ifat.
From: "Waines, Greg"
Date: Wednesday, 30 August 2017 at 22:17
To: "OpenStack Development Mailing List (not f
aph.
Let me know if it helped,
Ifat.
From: "Waines, Greg"
Date: Wednesday, 23 August 2017 at 21:19
I am trying to get collectd to report some alarms to vitrage in a devstack
setup,
I am using a devstack created on a late version of ocata.
And my devstack with vitrage appears to be work
Which is a tool build by the ironic team and used by ironic to deploy and
cleanup the baremetal nodes.
The cirros images are just the default images loaded by devstack, I believe by
default it downloads them from the cirros http://download.cirros-cloud.net
Sam
On 24/07/2017, 17:07, &
aster/magnum/drivers/k8s_fedora_atomic_v1/templates
[2]
https://github.com/openstack/magnum/tree/master/magnum/drivers/k8s_coreos_v1/templates
[3] https://bugs.launchpad.net/ironic/+bug/1666009
Mark
On 17 July 2017 at 14:27, Waines, Greg
mailto:greg.wai...@windriver.com>> wrote:
When MAGNUM launch
Hey Lucas,
Thanks for the pointer to this ironic devstack setup using VMs as baremetal
servers.
I was able to follow the recipe and get this working and play with ironic.
Of course I’ve got some follow up questions.
Questions on the images:
stack@devstack-ironic:~/devstack$ glance image-list
+
hey there,
I’m an ironic newbie ...
where can I find a good / relatively-current (e.g. PIKE) demo of Ironic
integrated within OpenStack ?
Greg.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
When MAGNUM launches a VM or Ironic instance for a COE master or minion node,
with the COE Image,
What is the interface configuration and assumptions for these nodes ?
e.g.
- only a single interface ?
- master and minion communication over that interface ?
- communication to Docker Registry or pub
I believe the MAGNUM architecture supports using either a VM Instance or an
Ironic Instance as the Host for the COE’s masters and minions.
How is this done / abstracted within the MAGNUM Architecture ?
i.e. is there a ‘container-host-driver API’ that is defined; and implemented
for both VM and I
n -i --name ctn-ping --image-driver glance cirros ping 8.8.8.8
Best regards,
Hongbin
From: Waines, Greg [mailto:greg.wai...@windriver.com]
Sent: July-12-17 1:01 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [zun] "--image-driver glance" do
What is expected for the “--nets network=...” parameter on zun run or create ?
Is it the network name, the subnet name, the network uuid, the subnet uuid, ...
I think I’ve tried them all and none work.
Full logs:
stack@devstack-zun:~/devstack$ neutron net-list
neutron CLI is deprecated and will
Just tried this, this morning.
I can not launch a container when I specify to pull the container image from
glance (instead of docker hub).
I get an error back from docker saying the “:latest” can not be
found.
I tried renaming the glance image to “:latest” ... but that didn’t
work either.
sta
ementation will be available at the next release or two.
Best regards,
Hongbin
From: Waines, Greg [mailto:greg.wai...@windriver.com]
Sent: July-11-17 10:24 AM
To: Hongbin Lu; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [zun] Some general ZUN use case
is to switch to
the Placement API [1] after it is spited out from Nova.
[1] https://docs.openstack.org/nova/latest/placement.html
Best regards,
Hongbin
From: Waines, Greg [mailto:greg.wai...@windriver.com]
Sent: July-07-17 11:00 AM
To: Hongbin Lu; OpenStack Development Mailing List (not for
s on it. I don’t have specific answers for the two questions
you raised but I encourage you to bring up your use cases to the team and keep
the discussion open.
[1] https://www.slideshare.net/hongbin034/clipboards/zun-deployment
Best regards,
Hongbin
From: Waines, Greg [mailto:greg.wai...@win
type
questions
Hi Greg,
Please find my replies inline.
Best regards,
Hongbin
From: Waines, Greg [mailto:greg.wai...@windriver.com]
Sent: July-06-17 11:49 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [zun] Some general ZUN use case / drivers type
questions
Apologize I have
Apologize I have some ‘newbie’ questions on zun.
I have looked a bit at zun ... a few slide decks and a few summit presentation
videos.
I am somewhat familiar with old container orchestration attempts in openstack
... nova and heat.
And somewhat familiar with Magnum for COEs on VMs.
Question 1:
s without too many specs. You are welcome to
write a blueprint-only description, and maybe send us (or add to the
blueprintß) a UI mock.
Let us know if you need any help with that.
Best Regards,
Ifat.
From: "Waines, Greg"
Date: Wednesday, 7 June 2017 at 1:33
To: "Afek, Ifat (Nokia
launchapd… the vitrage-dashboard team usually just implement
the features and do code reviews without too many specs. You are welcome to
write a blueprint-only description, and maybe send us (or add to the
blueprintß) a UI mock.
Let us know if you need any help with that.
Best Regards,
Ifat.
rate blueprint should be
added to Horizon to create the extension point in the page header.
David
On Wed, May 31, 2017 at 11:06 AM, Waines, Greg
mailto:greg.wai...@windriver.com>> wrote:
Hey Rob,
Just thought I’d check in on whether Horizon team has had a chance to re
scription, and maybe send us (or add to the
blueprintß) a UI mock.
Let us know if you need any help with that.
Best Regards,
Ifat.
From: "Waines, Greg"
Date: Wednesday, 7 June 2017 at 1:33
To: "Afek, Ifat (Nokia - IL/Kfar Sava)"
Subject: vitrage-dashboard blueprints / spec
t in the page header.
David
On Wed, May 31, 2017 at 11:06 AM, Waines, Greg
mailto:greg.wai...@windriver.com>> wrote:
Hey Rob,
Just thought I’d check in on whether Horizon team has had a chance to review
the following blueprint:
https://blueprints.launchpad.net/horizon/+spec/vitrage-alarm-
Has anyone seen the following behavior / issue ?
I am using Mitaka.
Sometimes ... with many users using the OpenStack installation,
I can be logged into Horizon as User-A/Tenant-A, on the Compute-->Instances
panel showing my running instances.
and then
For a few seconds (~3-4 seconds), my panel w
ject: Re: [openstack-dev] [masakari] Intrusive Instance Monitoring
Hi Greg,
Great.. thank you. I will ask people to review this..
--- Regards,
Sampath
On Tue, May 30, 2017 at 9:06 PM, Waines, Greg
mailto:greg.wai...@windriver.com>> wrote:
Hey Sam,
Was able to submit the blueprint and
for populating
that content if desired. This specific blueprint should really be
targeted at the Vitrage UI plugin and a separate blueprint should be
added to Horizon to create the extension point in the page header.
David
On Wed, May 31, 2017 at 11:06 AM, Waines, Greg
mailto:greg.wai...@windriver.
ueprints/patches etc.
Rob
On 18 May 2017 at 16:31, Waines, Greg
mailto:greg.wai...@windriver.com>> wrote:
A blueprint question for horizon team.
I registered a new blueprint the other day.
https://blueprints.launchpad.net/horizon/+spec/vitrage-alarm-counts-in-topnavbar
Do I need to do an
t 4:39 AM, Jeremy Stanley
mailto:fu...@yuggoth.org>> wrote:
On 2017-05-29 14:48:10 + (+), Waines, Greg wrote:
Was just trying to submit my spec for Intrusive Instance
Monitoring for review.
And I get the following warning after committing when I do the
‘git review’
gwaines@gwaines-Virtua
ot;
Date: Monday, May 29, 2017 at 3:39 PM
To: "openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [masakari] Intrusive Instance Monitoring
On 2017-05-29 14:48:10 +0000 (+), Waines, Greg wrote:
Was just trying to submit my spec for Intrusive Instance
Monitoring for r
nd
it will help masakari community and openstack-ha community to
understand the requirements and
support them in future developments.
[1] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117003.html
[2] https://github.com/openstack/masakari-specs
--- Regards,
Sampath
On Thu, May 18, 2017 at
017 at 2:29 AM, Adam Spiers
mailto:aspi...@suse.com>> wrote:
I don't see any reason why masakari couldn't handle that, but you'd
have to ask Sampath and the masakari team whether they would consider
that in scope for their roadmap.
Waines, Greg mailto:greg.wai...@windriver.com&g
A blueprint question for horizon team.
I registered a new blueprint the other day.
https://blueprints.launchpad.net/horizon/+spec/vitrage-alarm-counts-in-topnavbar
Do I need to do anything else to get this reviewed? I don’t think so, but
wanted to double check.
How frequently do horizon bluepri
( I have been having a discussion with Adam Spiers on
[openstack-dev][vitrage][nova] on this topic ... thought I would switchover to
[masakari] )
I am interested in contributing an implementation of Intrusive Instance
Monitoring,
initially specifically VM Heartbeat / Heath-check Monitoring thru
nes to this existing
one?
http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html
Waines, Greg mailto:greg.wai...@windriver.com>>
wrote:
Yes that’s correct.
VM Heartbeating / Health-check Monitoring would introduce intrusive / white-box
type monitor
stack-dev@lists.openstack.org"
Date: Tuesday, May 16, 2017 at 7:42 PM
To: "openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [vitrage] [nova] [HA] VM Heartbeat / Healthcheck
Monitoring
Waines, Greg mailto:greg.wai...@windriver.com>>
wrote:
Sam,
Two other
rage] [nova] [HA] VM Heartbeat / Healthcheck
Monitoring
Waines, Greg mailto:greg.wai...@windriver.com>>
wrote:
thanks for the pointers Sam.
I took a quick look.
I agree that the VM Heartbeat / Health-check looks like a good fit into
Masakari.
Currently your instance monitoring looks lik
Sam,
Two other more higher-level points I wanted to discuss with you about Masaraki.
First,
so I notice that you are doing both monitoring, auto-recovery and even host
maintenance
type functionality as part of the Masaraki architecture.
are you open to some configurability (enabling/disabling)
thanks for the pointers Sam.
I took a quick look.
I agree that the VM Heartbeat / Health-check looks like a good fit into
Masakari.
Currently your instance monitoring looks like it is strictly black-box type
monitoring thru libvirt events.
Is that correct ?
i.e. you do not do any intrusive type
nitoring tool like Zabbix, and then consume
the alarm (for a missing heartbeat) in Vitrage?
Best Regards,
Ifat.
From: "Waines, Greg"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, 10 May 2017 at 13:24
To: "OpenStack Developmen
Some other UPDATES on this proposal (from outside the mailing list):
· this should probably be based on an ‘image property’ rather than a
‘flavor extraspec’,
since it requires code to be included in the guest/VM image,
· rather than use a unique virtio-serial link for the
Hear
uot;
Date: Wednesday, May 10, 2017 at 9:49 AM
To: "openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck
Monitoring
On 5/9/2017 1:11 PM, Waines, Greg wrote:
I am looking for guidance on where to propose some “_VM Heartbeat /
Health-
I am looking for guidance on where to propose some “VM Heartbeat / Health-check
Monitoring” functionality that I would like to contribute to openstack.
Briefly, “VM Heartbeat / Health-check Monitoring”
· is optionally enabled thru a Nova flavor extra-spec,
· is a service that ru
I don’t think I saw any responses to this.
Alternative question ... so I’ve got vitrage up and running fine ...
What’s the easiest way to generate an alarm against a host ? ( OTHER than
NAGIOS, due to problem in original email ) ???
let me know any ideas,
Greg.
From: Greg Waines
Date: Tues
self, not in vitrage-dashboard.
Let me know if you need any assistance with this blueprint. Also, if you are
attending the Boston summit, we can meet and discuss it.
Best Regards,
Ifat.
From: "Waines, Greg"
Reply-To: "OpenStack Development Mailing List (not for usage questi
Any opinions on whether an Alarm Banner for the Vitrage Dashboard would be a
useful blueprint for improved usability ?
i.e. an ACTIVE Alarm Counts Banner in the Top Navbar of Horizon
· populated with the Active Alarm Counts for Critical, Major, Minor,
Warning Severities from Vitrage,
·
Hey ... I’m working thru the ‘Vitrage - Getting Started Guide’
https://docs.openstack.org/developer/vitrage/vitrage-first_steps.html
Was able to get vitrage up and running and enabled in horizon ... on ubuntu
16.04 .
( I tried on ubuntu 14.04 and ‘./stack.sh’ warned that it had not been
te
We have integrated a NEWTON-version of Murano into our OpenStack product.
And are beginning to do some testing of Murano.
Where can I find a current list of bugs that exist in NEWTON-version of MURANO ?
AND
Where can I find a list of post-NEWTON commits to MURANO ? (i.e. bug fixes,
enhancements,
I am running a NEWTON version of Murano.
When I try to import a package that is using io.murano.applications classes
(e.g. SingleServerApplication),
it seems to try to auto-import the liberty version of
io.murano.applications.zip … and fails.
Is this a bug ? Is it suppose to be using NEWTON v
LinuxMuranoInstance.
LinuxInstance doesn't try to build agent config and push it through cloud-init
and thus should not
have such problems
Regards,
Stan
On March 6, 2017 at 6:51:11 AM, Waines, Greg
(greg.wai...@windriver.com<mailto:greg.wai...@windriver.com>) wrote:
Hey Stan,
We tri
1 - 100 of 114 matches
Mail list logo
