- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Ignite: passing variables to scripts
Operating System - HP-UX
1748239
Members
3680
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2002 03:37 AM
тАО11-07-2002 03:37 AM
Ignite: passing variables to scripts
Hi admins:
Consider this configuration file for Ignite:
--snip--
# Adding Ignite's additional configuration controls
_OND_PROJECT = {
"BM",
"SMS"
}
_OND_PROJECT help_text "Reference platform project"
init _OND_PROJECT = "SMS"
_OND_PROJECT visible_if (sw_sel "OND reference platform archive")
init _OND_REF_PLAT = ""
_OND_REF_PLAT help_text "Reference platform name"
_OND_REF_PLAT visible_if (sw_sel "OND reference platform archive")
# Defining customization
sw_source "OND reference platform archive" {
description = "OND reference platform archive"
source_format = CMD
post_config_script += ${_OND_INSTALL_PATH}+"/scripts/ref_plat/custom/ref_plat_archive_creation.post_config"
# post_config_script += ${_OND_INSTALL_PATH}+"/scripts/common/make_sys_image -d /mnt/ref_plat -s local -n "+${system_name}+".gz -w /mnt/ref_plat/"+${system_name}+".log -m t -c g -l 2 -u -v"
final_script += ${_OND_INSTALL_PATH}+"/scripts/ref_plat/custom/ref_plat_archive_creation.final"
load_order = 5
}
sw_sel "OND reference platform archive" {
description = "OND scripts for reference platform archive creation"
sw_source = "OND reference platform archive"
sw_category = "OND"
exrequisite = "OND generic archive"
}
(sw_sel "OND reference platform archive") {
(_OND_PROJECT ~ "^[A-Za-z0-9_.-]+$") {
note += "OND project name validated."
env_vars = "_OND_PROJECT="+${_OND_PROJECT}
} else {
error += "OND project name contains one or more invalid characters. Installation cannot proceed."
}
(_OND_REF_PLAT ~ "^[A-Za-z0-9_.-]+$") {
note += "OND reference platform name validated."
env_vars = "_OND_REF_PLAT="+${_OND_REF_PLAT}
} else {
error += "OND reference platform name contains one or more invalid characters. Installation cannot proceed."
}
}
--snip--
This config file adds two controls in the 'Additional parameters' screen if ever user selects the sw_sel in the Software tab.
Now I check the syntax of variable _OND_REF_PLAT to make sure user has renamed it.
Once user has renamed it, I validate it and I would like to set the env_var _OND_REF_PLAT to it.
But Ignite does not change it once it has been initially set to ''...
I don't know how to set an additional parameter and pass it to an env_var once it has been modified, to make sure that my post_config scripts can use it.
Any idea?
Thanks!
/Brian
Consider this configuration file for Ignite:
--snip--
# Adding Ignite's additional configuration controls
_OND_PROJECT = {
"BM",
"SMS"
}
_OND_PROJECT help_text "Reference platform project"
init _OND_PROJECT = "SMS"
_OND_PROJECT visible_if (sw_sel "OND reference platform archive")
init _OND_REF_PLAT = "
_OND_REF_PLAT help_text "Reference platform name"
_OND_REF_PLAT visible_if (sw_sel "OND reference platform archive")
# Defining customization
sw_source "OND reference platform archive" {
description = "OND reference platform archive"
source_format = CMD
post_config_script += ${_OND_INSTALL_PATH}+"/scripts/ref_plat/custom/ref_plat_archive_creation.post_config"
# post_config_script += ${_OND_INSTALL_PATH}+"/scripts/common/make_sys_image -d /mnt/ref_plat -s local -n "+${system_name}+".gz -w /mnt/ref_plat/"+${system_name}+".log -m t -c g -l 2 -u -v"
final_script += ${_OND_INSTALL_PATH}+"/scripts/ref_plat/custom/ref_plat_archive_creation.final"
load_order = 5
}
sw_sel "OND reference platform archive" {
description = "OND scripts for reference platform archive creation"
sw_source = "OND reference platform archive"
sw_category = "OND"
exrequisite = "OND generic archive"
}
(sw_sel "OND reference platform archive") {
(_OND_PROJECT ~ "^[A-Za-z0-9_.-]+$") {
note += "OND project name validated."
env_vars = "_OND_PROJECT="+${_OND_PROJECT}
} else {
error += "OND project name contains one or more invalid characters. Installation cannot proceed."
}
(_OND_REF_PLAT ~ "^[A-Za-z0-9_.-]+$") {
note += "OND reference platform name validated."
env_vars = "_OND_REF_PLAT="+${_OND_REF_PLAT}
} else {
error += "OND reference platform name contains one or more invalid characters. Installation cannot proceed."
}
}
--snip--
This config file adds two controls in the 'Additional parameters' screen if ever user selects the sw_sel in the Software tab.
Now I check the syntax of variable _OND_REF_PLAT to make sure user has renamed it.
Once user has renamed it, I validate it and I would like to set the env_var _OND_REF_PLAT to it.
But Ignite does not change it once it has been initially set to '
I don't know how to set an additional parameter and pass it to an env_var once it has been modified, to make sure that my post_config scripts can use it.
Any idea?
Thanks!
/Brian
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2002 05:33 AM
тАО11-07-2002 05:33 AM
Re: Ignite: passing variables to scripts
I finally resolved my problem!
No need to answer.
I did not enclosed init keywords at the right place.
Regards,
/Brian
No need to answer.
I did not enclosed init keywords at the right place.
Regards,
/Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2002 05:41 AM
тАО11-07-2002 05:41 AM
Re: Ignite: passing variables to scripts
Oh, and i was hoping for 10 points :-) haha.
Chuck J
Chuck J
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2002 08:32 AM
тАО11-07-2002 08:32 AM
Re: Ignite: passing variables to scripts
Next time ;o)
Cheers.
/Brian
Cheers.
/Brian
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP