Could openstack create a server but without launch it - server

In my situation, we need to create a server only with shutoff status, but not active.
Is there any method to achieve that?

Related

zlogin usage in Runeck task

As part of rundeck task i'm trying to login to a global zone, use the command zoneadm list and trying to login to each of the local zone [to shut down various apps & to issue reboot] using the command /usr/sbin/zlogin and execute hostname command to ensure it did login to localzone
however this is not working
Is there a better way to do this? Please guide
Make sure that your job is dispatching to your remote node correctly, you can call the command on "Commands" (right panel) pointing to your node (referenced in the "Nodes" textbox) in that way you can discard possible path/user rights issue, take a look at this. Now, zlogin seems an interactive shell, and as you can see, you need to use it in the non-interactive mode.

Write Service in OPCUA Is returning BadWriteNotSupported

I am using OPCUA .net client and server SDKs. I Created a Node in Server from client using AddNodes Service. The node is not attached to any Model in the server. Then i tried to Write a value(eg 121) to the node. The write returned [BadWriteNotSupported]. Is there something I am doing wrong
Probably you created read-only node. Download UA Expert and inspect the node, it is very handy tool for second check.
It is because that node's Access level or user access level is read-only.
Mahe sure to set the access level and use access level for that now is read and write.
So that you can read and write a value to that node.

Changing config params without server reload in sails.js

Is it possible for Sails.js app to understand config file changes without having to restart server ? I want to add routes and change Mail server config params without server reboot. sails-hook-autoreload, seems to only cover models, controllers and services.
What are my options? I really do not want to restart the server when there are so many users logged into the app.
Please help. Thanks for reading the post
It isn't possible because the configs are only loaded into the app during start up. Your best bet to do scheduled maintenance and bring the app down and restart do your testing and then reopen the app to users.
I am not sure how to use it but I hear containers like Docker may be another solution where you containerize your app and use it to push updates out. Haven't used it but that could be a solution.

Problems with postgreSQL on ubuntu 12.10

I am a new postgresql user and I am trying to open an new account on this
database technology. As I was trying to open a new server I cannot create a database within this server. It says an error when I try to open that up.
Could you please tell whats wrong with this.
I do the following steps.
I create an account as this:
Despite this the server does not get created.
Is there something wrong with configuration of this server.
This is the error which says
Thank you in advance
Vangjush
The service is not the IP address of the server: http://www.pgadmin.org/docs/dev/connect.html
I'm no expert, but I believe the service is a shorthand for specifying other connection parameters. It's most simple to establish connections at first by specifying the values directly, so just leave that blank.
http://www.postgresql.org/docs/9.2/interactive/libpq-pgservice.html

OpenLdap redirect on write

I am currently trying to setup a redirect on write for an installation of OpenLdap 2.2.
I have two instances running. One is configured to be read-only (only read access, database specified as read-only) and has redirect configured to point to the second instance. The second instance is configured to allow for the desired write permissions.
When I attempt a modify on the first instance it fails as expected but does not send back the referral. Am I missing a piece of the configuration? Am I even on the right path? Any guidance would be greatly appreciated. Thanks.
In the database section of you slapd.conf do you add the redirection like this ? :
updateref "ldap://master-host:port/"
So, it turns out the best way to do this is to go ahead and set up replication using slurpd and point all requests at the slave instance. Unfortunately you can't set up the master and slave on the same host (for obvious reasons, but still), so I had to spin up a second VM to get this going.
Honestly, if I was not trying to replicate a redirect problem it wouldn't be worth it, but I have to duplicate a production issue.
For more information on slapd and specifically slurpd, the OpenLDAP documentation is actually crazy helpful: slurpd config for OpenLDAP 2.2