Rackspace Linux cloud servers now set OS-DCF:diskConfig to MANUAL when using nova. This means that the full drive isn't partitioned.
19:29:48 ~$ nova boot server01 --image 62df001e-87ee-407c-b042-6f4e13f5d7e1 --flavor performance2-60 --poll --key-name kylepub
+------------------------+---------------------------------------------+
| Property | Value |
+------------------------+---------------------------------------------+
| status | BUILD |
| updated | 2013-11-16T01:29:58Z |
| OS-EXT-STS:task_state | scheduling |
| key_name | kylepub |
| image | Ubuntu 13.04 (Raring Ringtail) (PVHVM beta) |
| hostId | |
| OS-EXT-STS:vm_state | building |
| flavor | 60 GB Performance |
| id | 9bd6aaac-bbdd-4644-821d-fb697fd48091 |
| user_id | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa |
| name | server01 |
| adminPass | XXXXXXXXXXXX |
| tenant_id | 864477 |
| created | 2013-11-16T01:29:58Z |
| OS-DCF:diskConfig | MANUAL |
| accessIPv4 | |
| accessIPv6 | |
| progress | 0 |
| OS-EXT-STS:power_state | 0 |
| config_drive | |
| metadata | {} |
+------------------------+---------------------------------------------+
How do I set OS-DCF:diskConfig to auto so the full disk is partitioned automatically?
Make sure you have os-diskconfig-python-novaclient-ext installed. If it's not, pip install it! It should come as part of installing rackspace-novaclient.
$ pip install os-diskconfig-python-novaclient-ext
Next up, use the --disk-config=AUTO option:
$ nova boot server01 --disk-config=AUTO --image 62df001e-87ee-407c-b042-6f4e13f5d7e1 --flavor performance2-60
Note that this is an extension by Rackspace, so if this is for a separate OpenStack deployment your provider needs the server side extension as well.
Big note: If you do the partitioning yourself, you are able to have non-EXT3 file systems, multiple partitions, and it lets you manage the disk configuration.
Related
I have this situation shown in the drawing.
I would like to configure the kubernetes pods so that they can talk to the external docker container "mysql", but I don't know how to configure it, especially regarding the IP address to tell them to connect to. I can't use "localhost" because that will just redirect back to the calling pod, I can't use 192.168.1.8 because the port is not exposed from there.
What is the DB Host IP in this case?
Thank you for any clues
+----------------------------------------------------------------------------------------------------------+
| |
| My Macbook Pro Laptop |
| |
| Today's DHCP IP: 192.168.1.8 |
| +-------------------------+ |
| | | |
| | K8s Cluster | |
| | | |
| | | |
| | K8s Pod | |
| | +---------------+ | |
| | | Docker | | |
| | | Container | | |
| | | +-----------+ | | |
| ??? | | | | | | |
| <-----------+ Foo | | | |
| +-------------+ | | | Program | | | |
| | Docker | | | | | | | |
| +-----------------------+ | container | Listening | | +-----------+ | | |
| | Local Hard Disk | | +---------+ | Port | +---------------+ | |
| | +------------------+ | | | | | 3306 | | |
| | | /Users/foo/data <------------- mysql <------+ | | |
| | | | | | | | | | K8s Pod | |
| | +------------------+ | | +---------+ | | +---------------+ | |
| +-----------------------+ +-------------+ | | Docker | | |
| | | Container | | |
| | | +-----------+ | | |
| ??? | | | | | | |
| <-----------+ Bar | | | |
| | | | Program | | | |
| | | | | | | |
| | | +-----------+ | | |
| | +---------------+ | |
| | | |
| | | |
| +-------------------------+ |
| |
| |
+----------------------------------------------------------------------------------------------------------+
Note Because of the current limitations of the kubernetes system available for MacOS, I cannot persist the data to the local hard disk (to a location of my choosing that I wish to specify) through kubernetes. I can do it however with Docker, so this is the only configuration I can find to achieve the desired goal of persisting the database files beyond the lifetime of the containers/pods
You can create External IP or External Name service with db host IP and call that service from POD.
Also other options is to deploy db as pod on k8 cluster with headless service.
Just out of curiosity, why you are deploying db as container using docker if you have k8 cluster?
I do not have OSX to test it, but that statement seems to be not true - that there is no way to persist data on Kubernetes for OSX. To do that you can just create a Persistent Volume which will be a resource in the cluster and then add PersistentVolumeClaim :
PV is is a resource in the cluster just like a node is a cluster
resource. PVs are volume plugins like Volumes, but have a lifecycle
independent of any individual pod that uses the PV.
PVC is a request for storage by a user. It is similar to a pod. Pods
consume node resources and PVCs consume PV resources. Pods can request
specific levels of resources (CPU and Memory). Claims can request
specific size and access modes (e.g., can be mounted once read/write
or many times read-only).
You can find explanation here. And how to here with step by step configuration of mySQL and in this case Wordpress.
About your setup, first try to follow the official documentation about running mySQL inside of the cluster (assuming you are using minikube, but if not there should't be much differences) if you do not succeed we will continue. I already started trying to connect from the inside of the cluster to mysql container outside (my setup is Ubuntu 18.04 with minikube).
Also you are right you won't be able to access it on localhost, because docker is actually using 172.17 (if I remember correctly) so you one of the options would be building new image and put host machine IP with exposed port.
I have installed openstack (Newton release) on Ubuntu 16.04 (all in one). every service is running well, but when I try to launch an instance, an error occurs:
Error: Failed to perform requested operation on instance "test1", the
instance has an error status: Please try again later [Error: No valid
host was found. There are not enough hosts available.].
When I enter:
[root#controller-hp ~(keystone_admin)]$ nova-hypervisor-list
+----+---------------------+-------+---------+
| ID | Hypervisor hostname | State | Status |
+----+---------------------+-------+---------+
| 1 | controller-hp | up | enabled |
+----+---------------------+-------+---------+
and the output of
[root#controller-hp ~(keystone_admin)]$ neutron ext-list
+---------------------------+-----------------------------------------------+
| alias | name |
+---------------------------+-----------------------------------------------+
| default-subnetpools | Default Subnetpools |
| network-ip-availability | Network IP Availability |
| network_availability_zone | Network Availability Zone |
| auto-allocated-topology | Auto Allocated Topology Services |
| ext-gw-mode | Neutron L3 Configurable external gateway mode |
| binding | Port Binding |
| metering | Neutron Metering |
| agent | agent |
| subnet_allocation | Subnet Allocation |
| l3_agent_scheduler | L3 Agent Scheduler |
| tag | Tag support |
| external-net | Neutron external network |
| flavors | Neutron Service Flavors |
| fwaasrouterinsertion | Firewall Router insertion |
| net-mtu | Network MTU |
| availability_zone | Availability Zone |
| quotas | Quota management support |
| l3-ha | HA Router extension |
| provider | Provider Network |
| multi-provider | Multi Provider Network |
| address-scope | Address scope |
| extraroute | Neutron Extra Route |
| shared_pools | Shared pools for LBaaSv2 |
| subnet-service-types | Subnet service types |
| standard-attr-timestamp | Resource timestamps |
| fwaas | Firewall service |
| service-type | Neutron Service Type Management |
| lb_network_vip | Create loadbalancer with network_id |
| l3-flavors | Router Flavor Extension |
| port-security | Port Security |
| hm_max_retries_down | Add a fall threshold to health monitor |
| extra_dhcp_opt | Neutron Extra DHCP opts |
| standard-attr-revisions | Resource revision numbers |
| lbaasv2 | LoadBalancing service v2 |
| pagination | Pagination support |
| sorting | Sorting support |
| lbaas_agent_schedulerv2 | Loadbalancer Agent Scheduler V2 |
| security-group | security-group |
| dhcp_agent_scheduler | DHCP Agent Scheduler |
| router_availability_zone | Router Availability Zone |
| lb-graph | Load Balancer Graph |
| rbac-policies | RBAC Policies |
| l7 | L7 capabilities for LBaaSv2 |
| standard-attr-description | standard-attr-description |
| router | Neutron L3 Router |
| allowed-address-pairs | Allowed Address Pairs |
| project-id | project_id field enabled |
| dvr | Distributed Virtual Router |
+---------------------------+-----------------------------------------------+
My nova.conf file is here:
https://paste.debian.net/1005278/
By using this guide, My network configuration is:
Network Overview
Name
physical01
ID
212248e9-71ff-4015-8fec-54567f38e92f
Project ID
43605ff65d2a40d19073e7268fd5d124
Status
Active
Admin State
UP
Shared
Yes
External Network
Yes
MTU
1500
Provider Network
Network Type: flat
Physical Network: physical01
Segmentation ID: -
and:
[root#controller-hp ~(keystone_admin)]$ neutron net-list
+--------------------------------+------------+--------------------------------+
| id | name | subnets |
+--------------------------------+------------+--------------------------------+
| 212248e9-71ff-4015-8fec- | physical01 | ee667189-bb7c-4861-81a0-2735d0 |
| 54567f38e92f | | 1c2011 10.1.79.0/24 |
+--------------------------------+------------+--------------------------------+
I use a large flavor for Cirros 0.3.4 64 bits image that is shows the problem doesn't relevant to resource.
that's the output of "tailf /var/log/neutron/neutron-*.log"
http://paste.openstack.org/show/648396/
These are my plugins configure:
ml2
Linux Bridge Agent
openvswitch
DHCP agent
L3 agent
I'd read these topics, but they couldn't solve my problem:
OpenStack Newton Installation(using packstack) Error
No valid host was found. There are not enough hosts available
...
Any help would be appreciated.
You may get clues from the following logs on compute nodes:
/var/log/nova/nova-scheduler.log
/var/log/neutron/neutron-*.log
I am developing a solution which involves reading messages from an Azure service bus queue using the BizTalk SB-Messaging adapter. I am using the BizTalk Deployment Framework to deploy the application without user input.
Some adapters have an option to acquire credentials for external systems using the Single Sign-On database (option 'Use SSO'). The SB-Messaging adapter doesn't have this feature, and requires that either ACS (Access Control Service) or SAS (Shared Access Secret) credentials for the service (in this case a queue) are entered in the UI. BTDF can also set them by entering them in the binding file (there is an attribute on those particular properties vt="[number]" which causes them to be ignored unless overriden, presumably to discourage the developer from storing credentials in cleartext.
How can I set the service bus credentials without them being kept in cleartext? For this scenario I consider any data written to disk or kept in source control to be cleartext, which means creating a bindings file containing these credentials is not acceptable.
I would ideally like this to just work, in the same way as the adapters which do support SSO. Is this possible?
(As an aside, anyone who knows why Microsoft apparently didn't bother to implement this would be welcome to air their views)
Yes the majority of the Adapters support SSO Affiliate applications or Use Single Sign-On for User Name credentials, however none of them support SSO Affiliate for ACS, SAS or for Proxy settings (see table below)
It seems the ones that don't support SSO Affiliate settings for the User Name credential are either the very old adapters, and strangely enough the newest ones.
Not having the SSO Affiliate settings for ACS, SAS or Proxy settings would look to be something they just didn't think about doing.
So to answer your question. No, it does not look to be possible to use SSO Affiliate with this adapter as you don't even have the option of adding a custom behavior as you can do with the WCF adapters, which is how we implemented a oAuth behavior to use SSO Affiliates to get the credentials & secrets for a WCF-WebHttp to Salesforce.
See also BizTalk Server 2013 R2: Adapters without Single Sign-On Capability and BizTalk Server 2013 R2: Adapters without Single Sign-On Capability on Technet
Use Single Sign-On or SSO Affiliate (BizTalk 2013R2)
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| Adapter | Receive | | | | | Send | | | |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| | Use | SSO | ACS/ | Proxy | Endpoint | SSO | ACS/ | Proxy | Endpoint |
| | SSO | Affiliate | SAS | | Behaviour | Affiliate | SAS | | Behaviour |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| File | No | No | - | - | - | No | - | - | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| FTP | No | Yes | - | No | - | Yes | - | No | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| HTTP | Yes | - | - | - | - | Yes | - | No | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| MQSeries | No | - | - | - | - | Yes | - | - | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| MSMQ | No | No | - | - | - | No | - | - | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| POP3 | No | No | - | - | - | - | - | - | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| SB-Messaging | No | - | No | - | - | - | No | - | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| SFTP | No | No | - | No | - | No | - | No | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| SMTP | - | - | - | - | - | No | - | - | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| SOAP | Yes | - | - | - | - | Yes | - | No | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| SQL | No | No | - | - | - | No | - | - | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-BasicHttp | Yes | - | - | - | in WCF-Custom | Yes | No | No | in WCF-Custom |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-BasicHttpRelay | No | - | No | - | No | Yes | No | No | No |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-Custom | Yes | Yes | - | - | Yes | Yes | No | No | Yes |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-CustomIsolated | Yes | Yes | - | - | - | - | - | - | - |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-NetMsmq | - | - | - | - | in WCF-Custom | Yes | - | - | in WCF-Custom |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-NetNamedPipe | Yes | - | - | - | in WCF-Custom | - | - | - | in WCF-Custom |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-NetTcp | Yes | - | - | - | in WCF-Custom | Yes | - | - | in WCF-Custom |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-NetTcpRelay | No | - | No | - | - | Yes | No | - | No |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-OracleDB | Yes | Yes | - | - | Yes | Yes | - | No | Yes |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-OracleEBS | Yes | Yes | - | - | Yes | Yes | - | No | Yes |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-SQL | Yes | Yes | - | - | Yes | Yes | - | No | Yes |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-WebHttp | Yes | - | - | - | Yes | Yes | No | No | Yes |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| WCF-WSHttp | Yes | - | - | - | in WCF-Custom | Yes | No | No | in WCF-Custom |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
| Windows | No | No | - | - | - | No | - | - | - |
| Sharepoint Server | | | | | | | | | |
+---------------------+---------+-------------+-------+-------+---------------+-------------+-------+-------+---------------+
I'm pretty sure the SB-Messaging uses SSO but keep in mind, there are two different patterns that Adapters use.
Some, such as the WCF wrappers, use the Credentials feature of SSO to store just the username/password combination. Others, such as the FTP's, store their entire config, including credentials, in SSO. SB-Messaging would follow this pattern.
If you have a 'don't store the password' rule, then you'll have to tread SB-Messaging like FTP. The Admin doing the deployment will have to enter the target specific credentials post-deploy. This is pretty common and really isn't a gap in any of the tools.
Another alternative is to create a custom MSBuild target for BTFD that modifies the binding file before Deploy. The custom task can read the credentials from SSO.
I m installing orocrm so i have an error during the installation process
this is my command php app/console oro:install error is [Symfony\Component\Process\Exception\RuntimeException]
The process timed-out.
i have check the oro_install.log file there is no any error
here is the instrucktion page i have followed http://www.orocrm.com/documentation/index/current/book/installation
thanks
this is my console
root#efttt-Intron-5t59:/home/eures/tance/crm-application/orocrm# php app/console oro:install
Installing Oro Application.
Oro requirements check:
+---------+------------------------------------------------------------------------------------------+ | Check | Mandatory requirements
|
+---------+------------------------------------------------------------------------------------------+ | OK | Vendor libraries must be installed
| | OK | app/cache/ directory must be writable
| | OK | app/logs/ directory must be writable
| | OK | Configured default timezone "Asia/Colombo" must be
supported by your installation of PHP | | OK | json_encode() must
be available
| | OK | session_start() must be available
| | OK | ctype_alpha() must be available
| | OK | token_get_all() must be available
| | OK | simplexml_import_dom() must be available
| | OK | PCRE extension must be available
| | OK | Cache folder should not be inside encrypted directory
|
+---------+------------------------------------------------------------------------------------------+
+---------+--------------------------------------------+ | Check | PHP settings |
+---------+--------------------------------------------+ | OK | date.timezone setting must be set | | OK |
detect_unicode must be disabled in php.ini | | OK | memory_limit
should be at least 512M |
+---------+--------------------------------------------+
+---------+------------------------------------------------------------------+ | Check | Oro specific requirements
|
+---------+------------------------------------------------------------------+ | OK | PHP version must be at least 5.4.9 (5.6.11-1ubuntu3.1
installed) | | OK | GD extension must be at least 2.0
| | OK | cURL extension must be at least 7.0
| | OK | mcrypt_encrypt() should be available
| | OK | intl extension should be available
| | OK | icu library must be at least 3.8
| | OK | web/uploads/ directory must be writable
| | OK | web/media/ directory must be writable
| | OK | web/bundles/ directory must be writable
| | OK | app/attachment/ directory must be writable
| | OK | web/js directory must be writable
| | OK | web/css directory must be writable
| | OK | app/config/parameters.yml file must be writable
|
+---------+------------------------------------------------------------------+
+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Check | Optional recommendations
|
+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | OK | Requirements file should be up-to-date
| | OK | When using the logout handler from the Symfony Security
Component, you should have at least PHP 5.4.11 due to PHP bug #63379
(as a workaround, you can also set invalidate_session to false in the
security logout handler configuration) | | OK | PCRE extension
should be at least version 8.0 (8.35 installed)
| | OK | PHP-XML module should be installed
| | OK | mb_strlen() should be available
| | OK | iconv() should be available
| | OK | utf8_decode() should be available
| | OK | posix_isatty() should be available
| | OK | intl extension should be available
| | OK | intl extension should be correctly configured
| | OK | intl ICU version should be at least 4+
| | OK | a PHP accelerator should be installed
| | OK | short_open_tag should be disabled in php.ini
| | OK | magic_quotes_gpc should be disabled in php.ini
| | OK | register_globals should be disabled in php.ini
| | OK | session.auto_start should be disabled in php.ini
| | OK | PDO should be installed
| | OK | PDO should have some drivers installed (currently
available: dblib, mysql, odbc)
| | OK | SOAP extension should be installed (API calls)
| | OK | A JS Engine (node) is installed
|
+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Dropping database schema... Database schema dropped successfully!
Clear the entity config cache Clear the extended entity cache Setting
up database. Process migrations...
Oro\Bundle\MigrationBundle\Migration\CreateMigrationTableMigration
Oro\Bundle\OrganizationBundle\Migrations\Schema\OroOrganizationBundleInstaller
Oro\Bundle\SecurityBundle\Migrations\Schema\v1_0\OroSecurityBundle
Oro\Bundle\AttachmentBundle\Migrations\Schema\OroAttachmentBundleInstaller
Oro\Bundle\EmailBundle\Migrations\Schema\OroEmailBundleInstaller
Oro\Bundle\UserBundle\Migrations\Schema\OroUserBundleInstaller
Oro\Bundle\SSOBundle\Migrations\Schema\OroUserBundleInstaller
Oro\Bundle\EntityConfigBundle\Migrations\Schema\OroEntityConfigBundleInstaller
Oro\Bundle\EntityConfigBundle\Migrations\Schema\v1_3\OroEntityConfigBundle
Oro\Bundle\EntityConfigBundle\Migrations\Schema\v1_4\FixOptionSetObjects
Oro\Bundle\EntityConfigBundle\Migrations\Schema\v1_5\DropFieldConfig
Oro\Bundle\EntityExtendBundle\Migrations\Schema\OroEntityExtendBundleInstaller
Oro\Bundle\EntityExtendBundle\Migrations\Schema\v1_3\OroEntityExtendBundle
Oro\Bundle\IntegrationBundle\Migrations\Schema\OroIntegrationBundleInstaller
Oro\Bundle\ActivityBundle\Migrations\Schema\OroActivityBundleInstaller
Oro\Bundle\ActivityListBundle\Migrations\Schema\OroActivityListBundleInstaller
Oro\Bundle\AddressBundle\Migrations\Schema\OroAddressBundleInstaller
Oro\Bundle\BatchBundle\Migrations\Schema\OroBatchBundleInstaller
Oro\Bundle\CalendarBundle\Migrations\Schema\OroCalendarBundleInstaller
Oro\Bundle\CalendarBundle\Migrations\Schema\v1_9\OroCalendarBundle
Oro\Bundle\ConfigBundle\Migrations\Schema\OroConfigBundleInstaller
Oro\Bundle\CronBundle\Migrations\Schema\v1_0\OroCronBundle
Oro\Bundle\CronBundle\Migrations\Schema\v1_0\JmsJob
Oro\Bundle\CronBundle\Migrations\Schema\v1_1\JmsJob
Oro\Bundle\DataAuditBundle\Migrations\Schema\OroDataAuditBundleInstaller
Oro\Bundle\DataGridBundle\Migrations\Schema\OroDataGridBundleInstaller
Oro\Bundle\EmbeddedFormBundle\Migrations\Schema\OroEmbeddedFormBundleInstaller
Oro\Bundle\ImapBundle\Migrations\Schema\v1_0\OroImapBundle
Oro\Bundle\ImapBundle\Migrations\Schema\v1_1\OroImapBundle
Oro\Bundle\ImapBundle\Migrations\Schema\v1_2\OroImapBundle
Oro\Bundle\InstallerBundle\Migrations\Schema\OroInstallerBundle
Oro\Bundle\MigrationBundle\Migrations\Schema\v1_0\OroMigrationBundle
Oro\Bundle\MigrationBundle\Migrations\Schema\v1_1\OroMigrationBundle
Oro\Bundle\NoteBundle\Migrations\Schema\v1_0\OroNoteBundle
Oro\Bundle\NoteBundle\Migrations\Schema\v1_1\OroNoteBundle
Oro\Bundle\NotificationBundle\Migrations\Schema\OroNotificationBundleInstaller
Oro\Bundle\ReportBundle\Migrations\Schema\OroReportBundleInstaller
Oro\Bundle\SearchBundle\Migrations\Schema\OroSearchBundleInstaller
Oro\Bundle\SegmentBundle\Migrations\Schema\OroSegmentBundleInstaller
Oro\Bundle\SidebarBundle\Migrations\Schema\v1_0\OroSidebarBundle
Oro\Bundle\SidebarBundle\Migrations\Schema\v1_1\OroSidebarBundle
Oro\Bundle\TagBundle\Migrations\Schema\OroTagBundleInstaller
Oro\Bundle\TranslationBundle\Migrations\Schema\OroTranslationBundleInstaller
Oro\Bundle\WindowsBundle\Migrations\Schema\v1_0\OroWindowsBundle
Oro\Bundle\WorkflowBundle\Migrations\Schema\OroWorkflowBundleInstaller
Oro\Bundle\CommentBundle\Migrations\Schema\v1_0\OroCommentBundle
Oro\Bundle\DashboardBundle\Migrations\Schema\OroDashboardBundleInstaller
Oro\Bundle\NavigationBundle\Migrations\Schema\v1_0\OroNavigationBundle
Oro\Bundle\NavigationBundle\Migrations\Schema\v1_1\OroNavigationBundle
Oro\Bundle\NavigationBundle\Migrations\Schema\v1_2\OroNavigationBundle
Oro\Bundle\NavigationBundle\Migrations\Schema\v1_3\OroNavigationBundle
OroCRM\Bundle\ContactBundle\Migrations\Schema\OroCRMContactBundleInstaller
OroCRM\Bundle\AccountBundle\Migrations\Schema\OroCRMAccountBundleInstaller
-------------------------------------------------------------------- >"Symfony\Component\Process\Exception\RuntimeException The process
timed-out."
probably due to dev log messages, try with the prod symfony env:
php app/console oro:install --env=prod
In the installation instruction on the github project page mention this note also:
Note: If the installation process times out, add the --timeout=0
argument to the command.
Hope this help
I am trying to impelment flywaydb in our process. In our env each client has their own instance of the DB.
I have a bash that loops through the clients to run migrate. So the command looks like
flyway -url=jdbc:jtds:sqlserver://localhost:1434/main_client_$ID migrate
This all works when all the clients start from the baseline. But as we add new customers their DB will reflect the newest code. Now we have older clients started with V1(and all the migration scripts to V2) and new clients with the latest DB V2.
I thought i could do something like :::
flyway baseline -url=jdbc:jtds:sqlserver://localhost:1434/main_client_3
--baselineVersion=2 --baselineDescription="Base 2 version"
but when i do it this way then call info i see something like :
+---------+-----------------------+---------------------+---------+
| Version | Description | Installed on | State |
+---------+-----------------------+---------------------+---------+
| 1 | << Flyway Baseline >> | 2015-06-08 22:07:54 | Success |
| 1.1 | update | | Pending |
| 1.2.0 | update | | Pending |
| 1.2.1 | update | | Pending |
+---------+-----------------------+---------------------+---------+
if i look in the DB i see the version value of schema_version set to 1.
if via the DB i force schema_version column value to 1.2.0 i see
+---------+-----------------------+---------------------+---------+
| Version | Description | Installed on | State |
+---------+-----------------------+---------------------+---------+
| 1 | Base version initial | | <Baseln |
| 1.1 | update | | <Baseln |
| 1.2.0 | << Flyway Baseline >> | 2015-06-08 22:07:54 | Success |
| 1.2.1 | update | | Pending |
+---------+-----------------------+---------------------+---------+
This is what i want.
But i can not figure out how to set the value via the baseline command
Thanks for any help
All parameters should be passed in with - not --