Task #4727
Story #4708: Test CN on Ubuntu 12.04
Upgrade dataone-cn-os-core
100%
Description
I decided to stage the upgrading. The first step is to test dataone-cn-os-core. We need to change the files, i.e., control, postinst and et al in https://repository.dataone.org/software/cicore/trunk/cn-buildout/dataone-cn-os-core/DEBIAN/ directory. Then do a upgrade.
I believe we need to uninstall those components before we upgrade the core:
dataone-cn-metacat
dataone-cn-portal
dataone-cn-rest-service
dataone-cn-processdaemon
dataone-cn-audit-index
dataone-cn-index
dataone-mercury
dataone-cn-solr
dataone-cn-version-tool
Associated revisions
refs #4727
modifying slapd for performance issues.
refs #4727
modifying slapd for performance issues.
refs #4727
modifying slapd for performance issues.
refs #4727
modifying slapd for performance issues.
refs #4727
modifying slapd for performance issues.
refs #4727
modifying slapd for performance issues.
refs #4727
modifying slapd for performance issues.
refs #4727
modifying slapd for performance issues.
refs #4727
modifying slapd for performance issues. reverting, does not like adding new indexes. should examine why later on.
refs #4727
modifying slapd for performance issues. reverting, does not like adding new indexes. should examine why later on.
refs #4727
modifying slapd for performance issues. reverting, does not like adding new indexes. should examine why later on.
refs #4727
modifying slapd for performance issues. reverting, does not like adding new indexes. should examine why later on.
refs #4727
modifying slapd for performance issues. reverting, does not like adding new indexes. should examine why later on. (mispelled indexname)
refs #4727
modifying slapd for performance issues. reverting, does not like adding new indexes. should examine why later on. (mispelled indexname)
refs #4727
modifying slapd for performance issues. reverting, does not like adding new indexes. should examine why later on. (mispelled indexname)
refs #4727
modifying slapd for performance issues. reverting, does not like adding new indexes. should examine why later on. (mispelled indexname)
refs #4727
modifying slapd for performance issues. reverting reverted. geez...
refs #4727
modifying slapd for performance issues. reverting reverted. geez...
refs #4727
modifying slapd for performance issues. reverting reverted. geez...
refs #4727
modifying slapd for performance issues. reverting reverted. geez...
refs #4727
openldap installation on debian has changed defaults:
from https://wiki.debian.org/LDAP/OpenLDAPSetup
For the DNS domain name, enter your domain name. This will be translated to an LDAP DN (for example, 'example.com' would become 'dc=example, dc=com'). This becomes what is known as your BaseDN, the root of your database.
This causes our initialization to fail. we need our basedn to be simple dc=org.
refs #4727
openldap installation on debian has changed defaults:
from https://wiki.debian.org/LDAP/OpenLDAPSetup
For the DNS domain name, enter your domain name. This will be translated to an LDAP DN (for example, 'example.com' would become 'dc=example, dc=com'). This becomes what is known as your BaseDN, the root of your database.
This causes our initialization to fail. we need our basedn to be simple dc=org.
refs #4727
openldap installation on debian has changed defaults:
from https://wiki.debian.org/LDAP/OpenLDAPSetup
For the DNS domain name, enter your domain name. This will be translated to an LDAP DN (for example, 'example.com' would become 'dc=example, dc=com'). This becomes what is known as your BaseDN, the root of your database.
This causes our initialization to fail. we need our basedn to be simple dc=org.
refs #4727
openldap installation on debian has changed defaults:
from https://wiki.debian.org/LDAP/OpenLDAPSetup
For the DNS domain name, enter your domain name. This will be translated to an LDAP DN (for example, 'example.com' would become 'dc=example, dc=com'). This becomes what is known as your BaseDN, the root of your database.
This causes our initialization to fail. we need our basedn to be simple dc=org.
refs #4727
openldap installation on debian has changed defaults:
from https://wiki.debian.org/LDAP/OpenLDAPSetup
For the DNS domain name, enter your domain name. This will be translated to an LDAP DN (for example, 'example.com' would become 'dc=example, dc=com'). This becomes what is known as your BaseDN, the root of your database.
This causes our initialization to fail. we need our basedn to be simple dc=org.
refs #4727
openldap installation on debian has changed defaults:
from https://wiki.debian.org/LDAP/OpenLDAPSetup
For the DNS domain name, enter your domain name. This will be translated to an LDAP DN (for example, 'example.com' would become 'dc=example, dc=com'). This becomes what is known as your BaseDN, the root of your database.
This causes our initialization to fail. we need our basedn to be simple dc=org.
refs #4727
openldap installation on debian has changed defaults:
from https://wiki.debian.org/LDAP/OpenLDAPSetup
For the DNS domain name, enter your domain name. This will be translated to an LDAP DN (for example, 'example.com' would become 'dc=example, dc=com'). This becomes what is known as your BaseDN, the root of your database.
This causes our initialization to fail. we need our basedn to be simple dc=org.
refs #4727
openldap installation on debian has changed defaults:
from https://wiki.debian.org/LDAP/OpenLDAPSetup
For the DNS domain name, enter your domain name. This will be translated to an LDAP DN (for example, 'example.com' would become 'dc=example, dc=com'). This becomes what is known as your BaseDN, the root of your database.
This causes our initialization to fail. we need our basedn to be simple dc=org.
refs #4727
configuring ldap needs to be more robust
refs #4727
configuring ldap needs to be more robust
refs #4727
configuring ldap needs to be more robust
refs #4727
configuring ldap needs to be more robust
refs #4727
configuring ldap needs to be more robust
refs #4727
configuring ldap needs to be more robust
refs #4727
configuring ldap needs to be more robust
refs #4727
configuring ldap needs to be more robust
History
#1 Updated by Robert Waltz almost 10 years ago
- Target version set to 2014.26-Block.4.1
#2 Updated by Robert Waltz almost 10 years ago
- Status changed from New to In Progress
- Assignee set to Jing Tao
- Milestone changed from None to CCI-1.2
- Product Version changed from * to 1.2.7
- Category set to d1_cn_buildout
#3 Updated by Robert Waltz almost 10 years ago
- Status changed from In Progress to Testing
#4 Updated by Robert Waltz almost 10 years ago
- translation missing: en.field_remaining_hours set to 0.0
- Status changed from Testing to Closed
