[Openstack] [barbican] Where to start understanding the crypto plugin API
Hi, I am new to Barbican and try to understand what it would take to implement the crypto plugin API. Could someone please point me to the right interface definition, and an example plugin? Thanks Andy Andreas Maier IBM Senior Technical Staff Member, OpenStack for z Systems IBM Research Development Laboratory Boeblingen, Germany mai...@de.ibm.com, +49-7031-16-3654 ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] IBM System Z
We are working with Michael directly; it turned out he's a colleague. I still wanted to give everybody on the list an update on the questions: Regarding the use of OpenStack on Linux on IBM z Systems, and the choice between different Linux distribution partners: IBM z Systems customers use both RHEL and SLES, and both distributions can be used to run OpenStack on z Systems. There are indeed some OpenStack dependencies that are not included in these distributions. Unless you want to be in the business of building, testing, distributing and servicing these missing packages for z Systems, I recommend to go with the following statement from the OpenStack Wiki (https://wiki.openstack.org/wiki/Get_OpenStack): The best way to install OpenStack is to rely on one of the downstream distributions, which will take care of many of the details for you.. Please contact me if you have trouble finding an OpenStack distribution that supports z Systems. In addition, regarding the use of OpenStack with the KVM hypervisor on IBM z Systems (starting with Kilo), I'd like to point to the second item (KVM offering for IBM z Systems) on this page: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=cainfotype=anappname=iSourcesupplier=877letternum=ENUSZG15-0001#sodx Finally, I'd like to point out that there is OpenStack support for the z/VM hypervisor as well, since several OpenStack releases. Andy Andreas Maier IBM Senior Technical Staff Member, OpenStack for z Systems IBM Research Development Laboratory Boeblingen, Germany mai...@de.ibm.com, +49-7031-16-3654 IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschaeftsfuehrung: Dirk Wittkopp Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 Forwarded Message From: Michael Lindner mich...@tropyx.com To: Openstack openstack@lists.openstack.org Subject: [Openstack] IBM System Z Date: Wed, 29 Jul 2015 07:37:25 +0930 Hi List, Has anyone used zLinux on s390x based mainframes to run Openstack? If so is RHEL or SLES better? NB I mean the whole stack, not just as a hypervisor. We're having issues with dependant packages not existing. Thanks, Mike. -- Michael Lindner IT Systems Consultant Sent from a Linux and Java based Android! ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[openstack-dev] [oslo] Changes to oslo.log section of Oslo Wiki page for source repo and bug reporting
Hello Dims 2. Can you please switch it to http://git.openstack.org/cgit/openstack/oslo.log/ ? If you see http://git.openstack.org/ you will see all the projects Done. Andy __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [oslo] Changes to oslo.log section of Oslo Wiki page for source repo and bug reporting
Hi, I'd like to notify the Oslo community of these two changes to the oslo.log section on the Oslo Wiki page: 1. There were conflicting statements about where bugs against oslo.log should be created: - The CONTRIBUTING.rst file in oslo.log suggests: https://bugs.launchpad.net/oslo.log - The oslo.log section on the Oslo Wiki page mentions: https://bugs.launchpad.net/oslo Based on where bugs are currently open, I suspected that the information on the Oslo Wiki page would be outdated, and updated it accordingly. 2. There was no link to a source repo yet for oslo.log on the Oslo Wiki page, so I added one to the github.com repo. If any of that was a bad idea, please let me know. Andy __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder] Feature Freeze Exception Request - bp/linux-systemz
Hello, I would like to ask for the following feature freeze exception in Cinder. The patch set below is part of this blueprint: https://blueprints.launchpad.net/cinder/+spec/linux-systemz 1. https://review.openstack.org/149256 - FCP support for System z Title: Adjust Cinder to support FCP on System z systems What it does: This patch set enables FCP support when the Cinder services run on System z. Impact if we don't get this: Cinder services cannot run on Linux for System z. A mitigation is to run Cinder services in on x86 Linux (even in an OpenStack installation that includes compute nodes with KVM on System z). Why we need it: We'd like to be able to support OpenStack installations where Cinder services run on System z Linux, which is the case for example in an all-in-one topology. Additional notes: The code in Nova patch set https://review.openstack.org/149256 is consistent with this patch set, but a decision to include them in kilo can be made independently for each of the two patch sets: The Nova patch set enables FCP storage for a compute node with KVM on System z, while the Cinder patch set enables Cinder services to run on System z Linux. Andy Andreas Maier IBM Senior Technical Staff Member, Systems Management Architecture Design IBM Research Development Laboratory Boeblingen, Germany mai...@de.ibm.com, +49-7031-16-3654 IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschaeftsfuehrung: Dirk Wittkopp Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] Feature Freeze Exception Request - bp/libvirt-kvm-systemz
Hello, I would like to ask for the following feature freeze exceptions in Nova. The patch sets below are all part of this blueprint: https://review.openstack.org/#/q/status:open+project:openstack/nova +branch:master+topic:bp/libvirt-kvm-systemz,n,z and affect only the kvm/libvirt driver of Nova. The decision for merging these patch sets by exception can be made one by one; they are independent of each other. 1. https://review.openstack.org/149242 - FCP support Title: libvirt: Adjust Nova to support FCP on System z systems What it does: This patch set enables FCP support for KVM on System z. Impact if we don't get this: FCP attached storage does not work for KVM on System z. Why we need it: We really depend on this particular patch set, because FCP is our most important storage attachment. Additional notes: The code in the libvirt driver that is updated by this patch set is consistent with corresponding code in the Cinder driver, and it has seen review by the Cinder team. 2. https://review.openstack.org/150505 - Console support Title: libvirt: Enable serial_console feature for system z What it does: This patch set enables the backing support in Nova for the interactive console in Horizon. Impact if we don't get this: Console in Horizon does not work. The mitigation for a user would be to use the Log in Horizon (i.e. with serial_console disabled), or the virsh console command in an ssh session to the host Linux. Why we need it: We'd like to have console support. Also, because the Nova support for the Log in Horizon has been merged in an earlier patch set as part of this blueprint, this remaining patch set makes the console/log support consistent for KVM on System z Linux. 3. https://review.openstack.org/150497 - ISO/CDROM support Title: libvirt: Set SCSI as the default cdrom bus on System z What it does: This patch set enables that cdrom drives can be attached to an instance on KVM on System z. This is needed for example for cloud-init config files, but also for simply attaching ISO images to instances. The technical reason for this change is that the IDE attachment is not available on System z, and we need SCSI (just like Power Linux). Impact if we don't get this: - Cloud-init config files cannot be on a cdrom drive. A mitigation for a user would be to have such config files on a cloud-init server. - ISO images cannot be attached to instances. There is no mitigation. Why we need it: We would like to avoid having to restrict cloud-init configuration to just using cloud-init servers. We would like to be able to support ISO images. Additional notes: This patch is a one line change (it simply extends what is already done in a platform specific case for the Power platform, to be also used for System z). Andy Andreas Maier IBM Senior Technical Staff Member, Systems Management Architecture Design IBM Research Development Laboratory Boeblingen, Germany mai...@de.ibm.com, +49-7031-16-3654 IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschaeftsfuehrung: Dirk Wittkopp Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
