I'm currently using ocata ROD distbution and l'm trying to implement openstack with glusterfs as a cinder volume. But I'm getting module load error.
Please advise if ocata is supporting glusterfs as a cinder volume.
According to :
https://docs.openstack.org/ocata/admin-guide/blockstorage-glusterfs-backend.html
"The GlusterFS volume driver, which was deprecated in the Newton release, has been removed in the Ocata release."
So Ocata release DOES NOT support glusterfs.
Related
I installed Heat service for Openstack Stein on my Ubuntu 18.04 LTS host following this link:
https://docs.openstack.org/heat/stein/install/install-ubuntu.html
but when i verify installation using this link:
https://docs.openstack.org/heat/stein/install/verify.html
I get the following result:
controller#controller:~$ openstack orchestration service list
WARNING: Failed to import plugin clustering.
ERROR: None
How I can solve it? Thanks in advance.
I am trying to create a cinder storage with a size of 5Gb and I get the following error.
# cinder create 5 --display-name FileStorage
ERROR: Version 3.52 is not supported by the API. Minimum is 3.0 and maximum is 3.50. (HTTP 406) (Request-ID: req-cc838137-0b60-4e72-8abe-a679a55aa399)
Is there any way I could get the cinder created ? I cannot change settings in openstack as I am not an admin. How do I go back version to 3.50 ?
Change the API version that cinder will use by setting an environment variable :
export OS_VOLUME_API_VERSION=3.50
We've built a CordApp which connects with RabbitMQ and requires a configuration file to configure the subscribers and publishers to the message queues.
The CorDapp is build against 3.2-corda but fails to load the configuration file when running on a Corda Enterprise 3.2 node.
The following exception is appended to the logs when we start the Corda web server:
Starting as webserver: localhost:8080 [ERROR] 11:59:24+0000 [main]
messaging.XXX.initializeQueues - Exception caught when subscribing to
Rabbit queues [ERROR] 11:59:24+0000 [main]
messaging.XXX.initializeQueues -
net.corda.nodeapi.internal.config.ConfigUtilities.parseAs(Lcom/typesafe/config/Config;Lkotlin/reflect/KClass;)Ljava/lang/Object;
java.lang.NoSuchMethodError:
net.corda.nodeapi.internal.config.ConfigUtilities.parseAs(Lcom/typesafe/config/Config;Lkotlin/reflect/KClass;)Ljava/lang/Object;
Nov 27, 2018 11:59:25 AM
org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
The code that loads the configuration is as follows:
val connectionConfig = defaultConfig!!
.resolve()
.getConfig("app-integration.rabbitMqConnectionConfiguration")
.parseAs<RabbitMqConnectionConfiguration>()
Given we are using a generic parseAs<RabbitMqConnectionConfiguration>() method, we assume that this is intended to subsequently call a parseAs(Config, KClass): Object method, but for some reason, it seems to be missing?
I would actually take a look at #joel's suggestion above. Corda is not an 'open core' project just yet.
So it's possible that you should compile the cordapps against the enterprise jar to determine whether the issue is the app or a different API between the two corda versions.
My other suspicion is that there might be different versions of java that are being used in the corda OS and the corda enterprise.
I would also see if this issue persists in the latest version of corda as well.
I installed cloudify3.4 according to the cloudify DOCS. When I install the manager, and executed like this:
# cfy bootstrap --install-plugins -p openstack-manager-blueprint.yaml -i openstack-manager-blueprint-inputs.yaml
an error occurred:
[ERROR] Bootstrap failed! (Workflow failed: Task failed 'neutron_plugin.floatingip.create' -> Expected exactly one object of type network with match {'name': u'178d7438-ca18-4df6-a5d0-dd11a53155a5'} but there are 0)
I have already installed
"cloudify_openstack_plugin-1.4-py27-none-linux_x86_64-centos-Core.wgn"
"cloudify_openstack_plugin-1.4-py27-none-linux_x86_64-redhat-Maipo.wgn"
So, how to solve this error?
Thank you to everyone who helped me!
In Cloudify version 3.4, the Cloudify manager can only be installed (bootstrapped) on either CentOS 7.x or RHEL 7.x.
See more details :
http://docs.getcloudify.org/3.4.0/manager/prerequisites/
FYI: There are no limitations in host agents.
That means that once the Cloudify manager is alive, it will enable you to deploy anything on every operating system.
I'm using Cloudify 2.7 with OpenStack Icehouse.
I have deployed with success a tomcat service.
In the Cloudify log, I see:
WARNING [org.cloudifysource.usm.tail.RollingFileReader] - In RollingFileReader: file not found
Can someone help me to understand the meaning of the error?
Thanks.
The Cloudify RollingFileReader is explained here:
https://github.com/CloudifySource/cloudify/blob/master/USM/src/main/java/org/cloudifysource/usm/tail/RollingFileReader.java
In this case, it means that Cloudify was expecting a log file to be created, but none was found. This is probably not a critical error.
Note that Cloudify 2 has reached End-of-Life. You should consider moving to Cloudify 3