Hi-
I am looking for the way to get system usage data for a billing purpose
in Diablo release. Is there anyone know as to how to get event messages
such as compute.instance.create, compute.instance.delete, etc? I believe
this information cat be retrieved via log files or AMQP.
P.S: I guess system
Blueprint changed by Vish Ishaya:
Priority: Undefined => Medium
--
XenAPI SM Volume Driver
https://blueprints.launchpad.net/nova/+spec/xenapi-sm-support
--
Mailing list: https://launchpad.net/~openstack-volume
Post to : openstack-volume@lists.launchpad.net
Unsubscribe : https://launchp
Blueprint changed by Vish Ishaya:
Whiteboard set to:
chap is passed back after cleanup branch. Needs to be verified that it
is implemented and works in both xen and kvm.
--
Chap Support for Nova Volume
https://blueprints.launchpad.net/nova/+spec/isci-chap
--
Mailing list: https://launchpad.ne
Blueprint changed by Vish Ishaya:
Assignee: (none) => Nova volume
--
Chap Support for Nova Volume
https://blueprints.launchpad.net/nova/+spec/isci-chap
--
Mailing list: https://launchpad.net/~openstack-volume
Post to : openstack-volume@lists.launchpad.net
Unsubscribe : https://launchpa
Blueprint changed by Vish Ishaya:
Approver: (none) => Vish Ishaya
--
XenAPI SM Volume Driver
https://blueprints.launchpad.net/nova/+spec/xenapi-sm-support
--
Mailing list: https://launchpad.net/~openstack-volume
Post to : openstack-volume@lists.launchpad.net
Unsubscribe : https://launc
Blueprint changed by Vish Ishaya:
Definition Status: Drafting => Approved
--
XenAPI SM Volume Driver
https://blueprints.launchpad.net/nova/+spec/xenapi-sm-support
--
Mailing list: https://launchpad.net/~openstack-volume
Post to : openstack-volume@lists.launchpad.net
Unsubscribe : https
Blueprint changed by Vish Ishaya:
Priority: Essential => High
--
Chap Support for Nova Volume
https://blueprints.launchpad.net/nova/+spec/isci-chap
--
Mailing list: https://launchpad.net/~openstack-volume
Post to : openstack-volume@lists.launchpad.net
Unsubscribe : https://launchpad.ne
Blueprint changed by Vish Ishaya:
Priority: Undefined => Essential
--
Chap Support for Nova Volume
https://blueprints.launchpad.net/nova/+spec/isci-chap
--
Mailing list: https://launchpad.net/~openstack-volume
Post to : openstack-volume@lists.launchpad.net
Unsubscribe : https://launchp
Blueprint changed by Vish Ishaya:
Definition Status: Drafting => Approved
--
Chap Support for Nova Volume
https://blueprints.launchpad.net/nova/+spec/isci-chap
--
Mailing list: https://launchpad.net/~openstack-volume
Post to : openstack-volume@lists.launchpad.net
Unsubscribe : https://
Blueprint changed by Vish Ishaya:
Assignee: Duncan Thomas => Nova volume
--
Nova Volume Snapshot / Backup API
https://blueprints.launchpad.net/nova/+spec/nova-volume-snapshot-backup-api
--
Mailing list: https://launchpad.net/~openstack-volume
Post to : openstack-volume@lists.launchpad.
Since affinity can be expressed as key-value pairs, that works fine for me too.
In our case no scheduler decision is needed, any volume diver instance will do,
but I guess for non-fully-connected storage then it becomes a scheduling
decision, so the interface should be something that the schedul
Hi Duncan,
I was thinking of using it as a “requirements” field for volume scheduling.
In this case it will be not a free-text, but dictionary of key/value pairs.
Unlike regular volume metadata field where user/app could put anything, this
one will be forwarded to scheduler and treated as a spec
Hi
I'm still working on the blueprint for affinity, but an optional free-text
field that gets passed through to the scheduler and driver should be fine from
a user api point-of-view.
Regards
--
Duncan Thomas
HP Cloud Services, Galway
From: openstack-volume-bounces+duncan.thomas=hp@lists.l
You don't need to do such hack, in fact, the lun number is not a bug here,
The node creates an iscsi session and have a new volume that appears into
/dev/sdX
That is that file descriptor which is used to attach a volume to a running
instance (check the instance's xml file if you want to check wh
I have modified three fils:
/usr/local/lib/python2.7/dist-packages/nova/virt/libvirt/volume.py
nova/volume/driver.py
nova/virt/libvirt/volume.py
change lun0->lun1
- host_device = ("/dev/disk/by-path/ip-%s-iscsi-%s-lun-0"
+ host_device = ("/dev/disk/by-path/ip-%s-iscsi-%s-lun-1"
it works well. b
15 matches
Mail list logo
