[JBoss JIRA] (DROOLS-3706) [DMN Designer] Boxed Expression - Improve title
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3706?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3706:
---------------------------------------
Summary: [DMN Designer] Boxed Expression - Improve title (was: [DMN Designer] Decision Navigator - Boxed Expression - Improve title)
> [DMN Designer] Boxed Expression - Improve title
> -----------------------------------------------
>
> Key: DROOLS-3706
> URL: https://issues.jboss.org/browse/DROOLS-3706
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> Improve the boxed expression title.
> - Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
> - Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
> ⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3706) [DMN Designer] Boxed Expressions - Enhance component title
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3706?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3706:
---------------------------------------
Summary: [DMN Designer] Boxed Expressions - Enhance component title (was: [DMN Designer] Boxed Expression - Improve title)
> [DMN Designer] Boxed Expressions - Enhance component title
> ----------------------------------------------------------
>
> Key: DROOLS-3706
> URL: https://issues.jboss.org/browse/DROOLS-3706
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> Improve the boxed expression title.
> - Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
> - Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
> ⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3706) [DMN Designer] Decision Navigator - Boxed Expression - Improve title
by Guilherme Carreiro (Jira)
Guilherme Carreiro created DROOLS-3706:
------------------------------------------
Summary: [DMN Designer] Decision Navigator - Boxed Expression - Improve title
Key: DROOLS-3706
URL: https://issues.jboss.org/browse/DROOLS-3706
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Guilherme Carreiro
Assignee: Guilherme Carreiro
Improve the boxed expression title.
- Rename "<< Back to <NODE_NAME>" (*"<< Back to Decision-1"*) to just *"<< Back"*
- Rename "<BOXED_EXPRESSION_TYPE>" (*"Decision Table"*) to "<NODE_NAME> (<BOXED_EXPRESSION_TYPE>)" (*"Decision-1 (Decision Table)"*)
⚠️ Notice: Check the latest Liz mockup for this task.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-617) Migrate our test ocp clusters to PSI
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-617?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-617:
-------------------------------------
its bug in Upshift Openstack
dont use same net as the server you run it from. then it will get wrong
domain openstaclocal
we opened a ticket on this
os_external_net: "provider_net_cci_5" <- dont set it to same net as is
attached to vm you run flexywrapper on
_____________________________________
Sasha Segal
Senior QE Engineer
Red Hat Israel
ssegal(a)redhat.com M: +972-52-2058824 IM: ssegal
On 2/25/19 2:10 PM, Filip Brychta wrote:
> Hi Sasha,
> thanks for quick response.
>
> I tried again with the latest changes (commit: 1b1546).
> First attempt failed because of "Timeout on http://download.eng.bos.redhat.com/rcm-guest/puddles/RHAOS/AtomicOpenShif..." - I believe this is out of scope of Flexywrapper
> Second attempt was successful.
> Third attempt failed because of "Quota exceeded for resources: ['router']." - Again out of scope of Flexywrapper. Just a heads up for others who read this, it seems that default quota for routers in PSI openStack is only 2.
>
> Notes:
> 1) successful attempt created cluster using internal domain names:
> TASK [print_access_details_openstack : debug] ***********************************************************
> ok: [localhost] => {
> "msg": [
> "Installation Summary - Your FlexyWrapper installation has completed successfully.",
> "The OpenShift admin portal is accessible via the following URL with no credentials:",
> "",
> "url: https://host-10-0-145-36.openstacklocal:8443/console/",
> " (use any user/pass)",
> "",
> "You may access the following cluster nodes directly via ssh:",
> "host-10-0-145-36.openstacklocal",
> "host-10-0-144-118.openstacklocal",
> "host-10-0-145-1.openstacklocal",
> ""
> ]
> }
>
> Is it possible to get domain names resolvable outside of OpenStack?
>
> 2) Please add a note to docs that Flexywrapper should not be run under root. Installation fails when run under root user, I believe it's because it's not possible to ssh to created VMs under root.
>
>
> Thank you,
>
> Filip
>
> ----- Original Message -----
>> Fillip,
>>
>> I fixed several issues during weekend and re-pointed tag v2.1 to updated
>> master.
>>
>> Please clone clean and try with tag v2.1
>>
>> Please note that I updated flexywrapper-params.yml so if you have it out
>> of directory, update it too.
>>
>> Let me know how it works for you.
>>
>> _____________________________________
>>
>> Sasha Segal
>>
>> Senior QE Engineer
>>
>> Red Hat Israel
>>
>> ssegal(a)redhat.com M: +972-52-2058824 IM: ssegal
>>
>> On 2/22/19 12:31 PM, Filip Brychta wrote:
>>> Hi Sasha,
>>> I tried to use the latest FlexyWrapper tag: v2.1 to spin up ocp 3.11 in PSI
>>> OpenStack. The VMs, network, subnet, router were created but the process
>>> failed with process timeout on "Gathering Facts" task in "Pre actions on
>>> all hosts in the cluster".
>>> Is this expected as this is still WIP or I should file a ticket for this? I
>>> assume that v1.1 is not usable for ocp 3.11 in PSI (OpenStack13) looking
>>> at commit "CID-3958 - Fix OpenStack13 support" which comes after v1.1 tag.
>>>
>>> Thank you,
>>>
>>> Filip
>>>
>>> Kiali QE
> Migrate our test ocp clusters to PSI
> ------------------------------------
>
> Key: SWSQE-617
> URL: https://issues.jboss.org/browse/SWSQE-617
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
>
> We need to answer following questions:
> * do we want to do that or stay in our bos lab
> * how to provision ocp clusters in PSI (Flexy? Flexy wrapper, LInchpin)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3705) [DMN Designer] Decision Navigator - Highlight selected nodes
by Guilherme Carreiro (Jira)
Guilherme Carreiro created DROOLS-3705:
------------------------------------------
Summary: [DMN Designer] Decision Navigator - Highlight selected nodes
Key: DROOLS-3705
URL: https://issues.jboss.org/browse/DROOLS-3705
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Guilherme Carreiro
Assignee: Guilherme Carreiro
Attachments: 2.gif
Currently, the Decision Navigator highlights only boxed expressions:
!2.gif|thumbnail!
The expected behaviour is to highlight nodes too.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3703) [DMN Designer] Data Types - Constraints - Disable Enumeration and Range components for Any/Context types
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3703?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3703:
---------------------------------------
Description:
Disable Enumeration and Range components for Any/Context types.
See (type vs. constraint dropdown):
{{*Any* - Expression}}
{{*boolean* - Disabled}}
{{*context* - Expression}}
{{*date* - Expression, Enumeration, Range}}
{{*date and time* - Expression, Enumeration, Range}}
{{*days and time duration* - Expression, Enumeration, Range}}
{{*number* - Expression, Enumeration, Range}}
{{*string* - Expression, Enumeration, Range}}
{{*time* - Expression, Enumeration, Range}}
{{*years and months duration* - Expression, Enumeration, Range}}
{{*Structure* - Disabled}}
was:
Disable Enumeration and Range components for Any/Context types.
See (type vs. constraint dropdown):
{{Any - Expression}}
{{boolean - Disabled}}
{{context - Expression}}
{{date - Expression, Enumeration, Range}}
{{date and time - Expression, Enumeration, Range}}
{{days and time duration - Expression, Enumeration, Range}}
{{number - Expression, Enumeration, Range}}
{{string - Expression, Enumeration, Range}}
{{time - Expression, Enumeration, Range}}
{{years and months duration - Expression, Enumeration, Range}}
{{Structure - Disabled}}
> [DMN Designer] Data Types - Constraints - Disable Enumeration and Range components for Any/Context types
> --------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3703
> URL: https://issues.jboss.org/browse/DROOLS-3703
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> Disable Enumeration and Range components for Any/Context types.
> See (type vs. constraint dropdown):
> {{*Any* - Expression}}
> {{*boolean* - Disabled}}
> {{*context* - Expression}}
> {{*date* - Expression, Enumeration, Range}}
> {{*date and time* - Expression, Enumeration, Range}}
> {{*days and time duration* - Expression, Enumeration, Range}}
> {{*number* - Expression, Enumeration, Range}}
> {{*string* - Expression, Enumeration, Range}}
> {{*time* - Expression, Enumeration, Range}}
> {{*years and months duration* - Expression, Enumeration, Range}}
> {{*Structure* - Disabled}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3703) [DMN Designer] Data Types - Constraints - Disable Enumeration and Range components for Any/Context types
by Guilherme Carreiro (Jira)
Guilherme Carreiro created DROOLS-3703:
------------------------------------------
Summary: [DMN Designer] Data Types - Constraints - Disable Enumeration and Range components for Any/Context types
Key: DROOLS-3703
URL: https://issues.jboss.org/browse/DROOLS-3703
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Guilherme Carreiro
Assignee: Guilherme Carreiro
Disable Enumeration and Range components for Any/Context types.
See (type vs. constraint dropdown):
{{Any - Expression}}
{{boolean - Disabled}}
{{context - Expression}}
{{date - Expression, Enumeration, Range}}
{{date and time - Expression, Enumeration, Range}}
{{days and time duration - Expression, Enumeration, Range}}
{{number - Expression, Enumeration, Range}}
{{string - Expression, Enumeration, Range}}
{{time - Expression, Enumeration, Range}}
{{years and months duration - Expression, Enumeration, Range}}
{{Structure - Disabled}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months