Skip to content
This repository has been archived by the owner on Mar 23, 2021. It is now read-only.

Ability to name contacts #26

Closed
dsposito opened this issue May 11, 2014 · 0 comments
Closed

Ability to name contacts #26

dsposito opened this issue May 11, 2014 · 0 comments

Comments

@dsposito
Copy link
Member

A customer or seller can have multiple contacts for various scenarios/preferences (home address, business address, shipping address, etc.). It would be helpful to be able to provide a name for each contact.

This issue is a prerequisite for issue #11 so that the names of the contacts can be displayed in the dropdown menu of existing contacts when creating a new payment method via the control panel.

A couple of questions for the community:

  • Should the new "name" field exist in the core contacts table or in the relational tables (customer_contacts, seller contacts)? I'm leaning towards the latter.
  • It seems as though "name" should be a "required" parameter when creating a new contact. Though not providing a name could default to "Contact {ID}". Any suggestions on a better default name?
@dsposito dsposito added this to the Volcano 1.0 milestone May 11, 2014
wangyuqing4 pushed a commit to wangyuqing4/volcano-1 that referenced this issue Apr 30, 2019
[Issue volcano-sh#26]fix Delay Pod Creation

If **PG.Phase != v1alpha1.PodGroupInqueue**, do reclaim, allocate, backfill, preempt action.

<br/>

minA is 1,  pods total num is 100,  1 pod Running -> PG is Running,

PG Running != v1alpha1.PodGroupInqueue, resource shortage

can't do other actions. resource can not release, so 99 pods will always Pending.

<br/>

so fix **PG.Phase == v1alpha1.PodGroupPending**.

Issues info:
Issue ID: 26
Title: Delay Pod Creation
Issue url: CBU-PaaS/Community/volcano/volcano#26


See merge request CBU-PaaS/Community/volcano/volcano!113
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant